[AccessD] Access97 on W2000 crashes

Just something else to check.
This will tell you the version of DAO is in use within Access97 mdb
It will return either 3.51 or 3.6, you can use either with Access 97
depending on your reference settings.

Debug.Print DAO.DBEngine.Version

You might want to check you OS environment to see what Jet SP you are 
running
on your home machines and client. You can do this in code but this maybe 
quicker.

I have Jet SP8 installed
right click on these files in explorer then  select properties
Version Tab and look at the File Version Number

DAO 3.51
C:\WINDOWS\system32\msjet35.dll

3.51.3328.0

DAO 3.6
C:\WINDOWS\system32\msjet40.dll

4.00.8618.0


To find which older versions you maybe running insert above dll names
in DLL Help database to get older version numbers and what product 
installs them.

http://support.microsoft.com/dllhelp/

Andy Lacey wrote:

>Well I'm not doing anything clever but it is working. And yes, if I exit and
>reopen the app the compile is greyed out. The code I call at the start is
>below. The sequence is that the desktop icon runs the mdb with a /X to run a
>specific macro. The macro calls a function to handle all my starting up
>stuff, and that, fairly early on, calls the Recompile function.
>
>Function Recompile
>If Application.IsCompiled = False Then
>Call SysCmd(504, 16483)
>End If
>End Function
>
>So, if I decompile and run my icon it recompiles and saves (and you can
>watch the progress meters). If I exit and then run again it does not now
>recompile. Is that unusual?
>
>Bear in ind this is A97. Don't know if your experience is on later versions.
>
>--
>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: 11/01/06 10:21
>
>
>Hi Andy
>
>OK, I see. But still, the simple fact is (or at least was) that code cannot
>compile and save itself and stay compiled and saved ...
>
>If you close the app and reopen it without running anything (holding down
>Shift while launching) and check "Compile and save all modules", is this
>greyed out?
>If so I would very much like to know how you do it - after you have resolved
>your urgent issue, of course.
>
>/gustav
>
>  
>
>>>>andy at minstersystems.co.uk 11-01-2006 00:21 >>>
>>>>        
>>>>
>No, sorry to confuse Gustav. When I said I could see it I menat I can see
>the Compile progress indicator, then the Save one.
>
>-- 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 19:55
>>To: accessd at databaseadvisors.com
>>Subject: Re: [AccessD] Access97 on W2000 crashes
>>
>>
>>Hi Andy
>>
>>Hmm, if you can "see it working", I guess you run it from the
>>Immediate window. That works, but it is not the same as
>>calling it from code - that's the trap. But I'm not saying
>>this is the key to the solution, only that you may think the
>>code gets compiled and saved while it perhaps doesn't.
>>
>>I would follow Shamil's advice closely and track down the
>>offending code lines. Then rewrite the code.
>>
>>Once I had some very simple code (no API, no dll) that worked
>>perfectly here and on the client's Win2000 machines. On her
>>Win98 machines the app crashed much like yours - just poof
>>and no Access. I rewrote the code and the problem was gone.
>>
>>/gustav
>>
>>    
>>
>>>>>andy at minstersystems.co.uk 10-01-2006 19:12:14 >>>
>>>>>          
>>>>>
>>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?
>>    
>>
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada