[AccessD] Access97 on W2000 crashes

Andy,

If you:

1. Do not change references on runtime;
2. Do not create forms/reports on runtime;
3. Do not allow your users to change design of your forms/reports on design
time and to edit your code -

then your app should work OK compiled into MDE.

If you do change references on runtime then reconsider this part of your
app's coding and use RefLibPaths.

If you do create forms/reports on runtime or allow users to change design of
your forms/reports then split your monolith app's mdb into constant and
changing parts. (This may involve quite some refactoring or go smoothly
depending of your coding but when done this will work for sure - in one of
the MS Access 97 apps I worked on we had one root program  mdb and up to 40
mde program components.... In your case these could be just two parts but in
general case any big application can/should be split into many parts working
together in ensemble...)

Shamil

----- Original Message ----- 
From: "Andy Lacey" <andy at minstersystems.co.uk>
To: "'Access Developers discussion and problem solving'"
<accessd at databaseadvisors.com>
Sent: Tuesday, January 10, 2006 10:26 AM
Subject: Re: [AccessD] Access97 on W2000 crashes


> Interesting thought Shamil, thanks. I'll try today to see if that cures
it.
> However I have a horrible feeling that will open up other problems. I've
no
> experience with MDEs, never had the need, but have the lurking suspicion
> that there are things you can do with MDBs that you can't with MDEs - and
I
> probably do them.
>
> Andy
>
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com
> > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> > Shamil Salakhetdinov
> > Sent: 09 January 2006 22:43
> > To: Access Developers discussion and problem solving
> > Subject: Re: [AccessD] Access97 on W2000 crashes
> >
> >
> > > Yes there's just one (v large) FE. No library MDBs or MDEs.
> > OK, if this MDB is compiled and saved then when you run it on
> > another PC with other versions of referenced DLLs then it
> > can/will get lost its compiled state - I have had such
> > problem a long ago with a large MS Access frontend - and it
> > did crash unexpectedly as in your case. The solution was to
> > compile it into .mde...
> >
> > Shamil
> >
<<< tail skipped>>>