[AccessD] Access97 on W2000 crashes

Hi Marty, thanks for the suggestions but it's an Access 97 MDB, so some of
these don't apply. And it's not actually a corrupt MDB as it runs (and has
done for years) under W98 and, in many situations, under W2K and XP too.

-- Andy Lacey
http://www.minstersystems.co.uk 

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of 
> MartyConnelly
> Sent: 10 January 2006 19:44
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Access97 on W2000 crashes
> 
> 
> Check you are using Windows 2000 Service Pack 3 (SP3)  to stop oplock 
> problems
> When compiling make sure Track name AutoCorrect  is off
> can lead to corruption problems.
> Tools >> Options >> General >>.Track name AutoCorrect info 
> should be off.
> 
> Alan Browne has this suggestion http://allenbrowne.com/ser-25.html
> 
> In your subforms, include a text box for each field in its 
> LinkChildFields property. This simple step avoids frequent but 
> intermittent crashes of Access 2002 and 2003 ("... shut down by 
> Windows..."). The text boxes can be hidden if you do not wish 
> to see the 
> foreign key fields.
> 
> Or Tony Toews corruption FAQ
> 
> http://www.granite.ab.ca/access/corruptmdbs.htm
> 
> Andy Lacey wrote:
> 
> >But the SysCmd does work for me Gustav. I see it working, 
> compilng and 
> >saving. My problem's almost the very reverse as far as I can see. My 
> >references all show as ok. Nothing broken. Nothing failing 
> to compile. 
> >Nothing to mend. It's just that something flipping well 
> crashes despite 
> >that. And, as I said, it's when the MDB has been decompiled and 
> >therefore my Syscmd runs that everything works (see my post 
> that begins 
> >"Well it's not an issue anyway"). My problems come when I 
> exit and then 
> >reload the by-now-compiled MDB. Any ideas?
> >
> >Any ideas from anyone who's ben following this?
> >
> >Yours desperately
> >
> >-- Andy Lacey
> >http://www.minstersystems.co.uk
> >
> >
> >  
> >
> >>-----Original Message-----
> >>From: accessd-bounces at databaseadvisors.com
> >>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of 
> >>Gustav Brock
> >>Sent: 10 January 2006 15:51
> >>To: accessd at databaseadvisors.com
> >>Subject: Re: [AccessD] Access97 on W2000 crashes
> >>
> >>
> >>Hi Andy
> >>
> >>First, if the issue is a dll, one (fast) thing to check is if
> >>any exists in more than one folder. If so, and you can't sort 
> >>that out, use RefLibPaths.
> >>
> >>Then, SysCmd(..) run from code will not compile and save the
> >>code. It must be done from outside a code module which means 
> >>manually (as we, the developer, do) or from a macro. 
> >>Brilliant idea from Charlotte. 
> >>It is not that difficult to implement. Read closely here from 
> >>the old thread:
> >>
> >>  Broken References in Runtime AXP and A97. Solved!
> >>
> >>  
> >>http://databaseadvisors.com/mailman/htdig/accessd/2003-July/01
> >>    
> >>
> >1034.html
> >
> >Note the extended test for broken references.
> >
> >/gustav
> >
> >  
> >
> >>>>andy at minstersystems.co.uk 10-01-2006 14:52:32 >>>
> >>>>        
> >>>>
> >I've listed below the results of running ListRefs on the two 
> machines. 
> >At first I thought they were identical, but there is one 
> difference in 
> >the path to the Outlok library. Under W98 this is
> >
> >C:\PROGRAM FILES\MICROSOFT OFFICE\OFFICE\msoutl9.olb
> >
> >whereas W2K has the old-fashioned DOS'y path of
> >
> >C:\PROGRA~1\MICROS~1\Office\msoutl9.olb
> >
> >Surely this is not significant. It can't be, can it?
> >
> >The other thing I thought odd was that the DAO 3.5 reference 
> returns a 
> >.Major and .Minor of 4.0 not 3.5, but then again it's the 
> same on both 
> >machines.
> >
> >
> >  
> >
> 
> -- 
> Marty Connelly
> Victoria, B.C.
> Canada
> 
> 
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com 
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 
>