Re: Access 2000 to Access 2003 conversion
- From: "Andy G" <ajgould@xxxxxxxxxxx>
- Date: Tue, 13 Sep 2005 14:14:46 -0500
How can I make changes when it crashes before I can do anything? Will this
bug be fixed or is it not a bug anymore? Just wondering b/c this is
effecting a lot of applications we suport!
Thanks
Andy
"Allen Browne" <AllenBrowne@xxxxxxxxxxxxxx> wrote in message
news:uzDLgSrrFHA.908@xxxxxxxxxxxxxxxxxxxxxxx
> Hi bignerd
>
> To avoid the security warning in A2003, change the setting under:
> Tools | Macro | Security
> If you don't see that option, reset the menu. Right-click on the space to
> the right of the toolbar, and choose Customize. On the Toolbars tab,
> select the Menu Bar, and click Reset.
>
> The crash sounds like the new bug in A2002 and 2003 where they crash on a
> form that has a subform. To cut a long story short, you need to add a text
> box to the subform for the field(s) named in the LinkChildFields property
> of the subform. More info:
> http://allenbrowne.com/ser-48.html
> It's #2 in the Usability section of the article.
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia.
> Tips for Access users - http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
> "bignerd" <eric@xxxxxxxxxxxxxxx> wrote in message
> news:1125546936.969379.238060@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> We unfortunately were given a laptop this year to run an application
>> that I wrote for MS Access 2000 (my first access app), so I ran Tools:
>> Converter on it.
>>
>> Configuration
>> 1. The app is running on a Windows XP Pro machine
>> 2. The office 2003 has all the latest service packs - I've verified the
>> Jet, MDAC and Access 2003 SPs are the latest.
>> 3. The crash happens when I navigate from a multi-record "launch page"
>> (you double click a record) to a master detail form that shows the
>> details for that current record.
>> 4. The program uses all DAO code as I was under the impression that DAO
>> was what the forms and reports used internally anyway, and the MS VBA
>> 2000 book I had did not mention anything about ADO.
>> 5. The application has about 30 forms, 5 reports, 20 tables, 2 modules,
>> and about 60 queries.
>>
>> When it runs now, it experiences a number of problems:
>> 1. It constantly shuts down and displays a [Send Error Report] dialog.
>> The event id in the event log is 1000.
>> 2. On startup it gives a security violation - the help says I can set
>> it to low and it wil run fine. I don't have any resources on access
>> 2003 (well, help), and figured I'd dive into this one AFTER #1 was
>> addressed. I didn't remember putting any macros in the code as I was
>> writing it all in VBA.
>>
>> Is there soomething I can do - step-by-step, to resolve this? I really
>> can't "go back" to the 2000 version as I've been trying to implement
>> fixes in this new release due to requirements that are changing and
>> this is the only hardware I have to run it on at this point.
>
>
.
- Follow-Ups:
- Re: Access 2000 to Access 2003 conversion
- From: Allen Browne
- Re: Access 2000 to Access 2003 conversion
- References:
- Access 2000 to Access 2003 conversion
- From: bignerd
- Re: Access 2000 to Access 2003 conversion
- From: Allen Browne
- Access 2000 to Access 2003 conversion
- Prev by Date: Re: Upsizing with picture data
- Next by Date: Re: Access 2000 to Access 2003 conversion
- Previous by thread: Re: Access 2000 to Access 2003 conversion
- Next by thread: Re: Access 2000 to Access 2003 conversion
- Index(es):
Relevant Pages
|
