Andy Lacey
andy at minstersystems.co.uk
Mon Jan 9 16:03:24 CST 2006
Thanks for the link Shamil, I'll investigate. Yes there's just one (v large) FE. No library MDBs or MDEs. Andy > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of > Shamil Salakhetdinov > Sent: 09 January 2006 21:54 > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Access97 on W2000 crashes > > > Andy, > > Do you have just one front-end program mdb database or this > mdb refers to the other (library) .mdb/.mde databases? Do you > haev your front-end program mdb database's code compiled and saved? > > Shamil > > P.S. I still hope you can solve the problem without > investigating the list of loaded .dlls etc. but if you will > need that here is the code you can use: > > http://www.vbaccelerator.com/home/VB/Tips/Getting_Process_Info > rmation_Using_PSAPI/VB_PSAPI_Demonstration.asp > > combined with GetFileVersionInfo API call... > > ----- Original Message ----- > From: "Andy Lacey" <andy at minstersystems.co.uk> > To: "'Access Developers discussion and problem solving'" > <accessd at databaseadvisors.com> > Sent: Monday, January 09, 2006 11:26 PM > Subject: Re: [AccessD] Access97 on W2000 crashes > > > > Well I've moved on but not solved the problem. Importing everything > > into a new mdb didn't do it, so I decided to see if WXP had > the same > > problem. The answer was almost but not quite. It didn't > give the error > > message, instead it just dropped out of Access clean as a > whistle - no > > meesage, no nothing. So, I reckon, same problem just looks > different > > under XP. Now I've come > home > > to my own XP machine and run the app and no sign of a > problem. I now > > have > to > > think - why does an XP machine at work fail but not mine > here? Would > > it be reasonable to think it's a DLL issue? And could the > following be > > a factor? At work I long ago created a distributable version on the > > network so we could use Runtime. So even though we later installed > > full Access > everywhere > > we still install from the network Setup and use /Runtime. > At home I've > never > > done that. It's not the /Runtime itself cos I've tried > without it, but > does > > the fact that the MDB is installed by a distributable runtime setup > > mean that it's using different DLL's than a version just > running under > > a normal Access installation? I'm sure I've explained that > badly, but > > the nub is: > a) > > does anyone know how I can establish a full list of DLLs involved in > running > > the MDB, and b) how can I easily compare versions of said > DLLs on two > > machines? > > > > > > -- 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: 09 January 2006 14:08 > > > To: accessd at databaseadvisors.com > > > Subject: Re: [AccessD] Access97 on W2000 crashes > > > > > > > > > Hi Andy > > > > > > Yes, I see the problem. > > > But the import thing - if it should be the cure - should > really be a > > > one-timer. If it works, proceed evolution on the fresh > version as it > > > should work on W98 as well. > > > > > > /gustav > > > > > > >>> andy at minstersystems.co.uk 09-01-2006 14:50:04 >>> > > > Mmm, well there may be a Debug.Print around in a called routine > > > somewhere I guess. I'll take a look. I've decomp'd and > recomp'd on > > > the W2K machine but not done the new MDB thing. I could > try but it'd > > > be a nightmare scenario. The MDB is in constant evolution and I > > > couldn't contemplate having to do that every time. Madre > mia! Still, > > > I guess it'd be worth knowing if it cures the problem. Thanks > > > Gustav. Any other suggestions welcomed (very, very much). > > > > > > -- > > > Andy Lacey > > > http://www.minstersystems.co.uk > > > > > > > > > > > > > > > --------- Original Message -------- > > > From: "Access Developers discussion and problem solving" > > > <accessd at databaseadvisors.com> > > > To: "accessd at databaseadvisors.com" <accessd at databaseadvisors.com> > > > Subject: Re: [AccessD] Access97 on W2000 crashes > > > Date: 09/01/06 13:24 > > > > > > > > > Hi Andy > > > > > > I had a similar thing which I tracked down to a line with > > > Debug.Print. Commented this out and the code ran, believe > it or not. > > > However, that was not intermittent but consistent. > > > > > > Have you been through the usual tools: decompile and recompile on > > > Win2000? Or - still on Win2000 - import all objects in a new file? > > > > > > /gustav > > > > > > >>> andy at minstersystems.co.uk 09-01-2006 14:07:32 >>> > > > Help guys > > > > > > I have this Access 97 MDB (FE and BE both A97) which has been > > > running for years, mostly on W98 but also for some time > on W2K. Last > > > week something new happened. 2 users who were previously > on W98 went > > > to W2K. They use a part of the system which others don't, or at > > > least they try to but when they do it regularly crashes with: > > > > > > "Msaccess.exe has generated errors and will be closed by Windows. > > > You will need to restart the program. An error log is being > > > created." > > > > > > > > > -- > > > AccessD mailing list > > > AccessD at databaseadvisors.com > > > http://databaseadvisors.com/mailman/listinfo/accessd > > > Website: http://www.databaseadvisors.com > > > > > > > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > >