Lost compile in different PCs

[SD]

Hi,

I have been struggling with this problem for two days.

My development PC is running Windows XP/Office 97. The work stations are
running Windows 2000/Office 97. In the past I have always compile the
Access front end file in the developments PC before letting the staff
copy the access file. Since two days ago, despite the access file is
compiled in my development PC, the client's system complains it is not
compiled. (using IsComplied() function)

I have reinstalled Office 97 in my PC, applied SR1 and SR2b. I have also
decompiled the access file before compiling. It just won't stay compiled
in clients' PC. If I compile the access file using Clients' PC, then I
don't have this problem. I first thought this may be caused by recent
code changes, but I pulled out an old version and compiled, it had the
same problem.:(

So looks like my PC can no longer fully compile access files. There
isn't software change I can recall in my PC, other than automated MS
upgrade.

Any hint you can provide to put me in the right direction?
Thanks.

[Allen Browne]

What happens if you give the users an MDE? An MDE cannot decompile.

It would be interesting to track down *what* was causing the decompile. If
the database is opened bypassing any startup code (e.g. holding down Shift)
is it instantly decompiled?

According to michka, there are actually 11 states of decompilation, so the
yes/no answer is a little simplistic:
http://www.trigeminal.com/usenet/usenet004.asp?1033

It may be worth tracking down any differences in the files on the two
installations: msaccess.exe, msjet40.dll, and any libraries references under
Tools | References (from a code window).

There are some areas where Access 97 behaves differently under WinXP than
Win2000 and earlier, e.g. the Count of Controls in the Section of a Report.
I would not expect this to cause a decompile though.

--
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.

"SD" <[e-mail]> wrote in message
news:fi********************************@4ax.com...

Hi,

I have been struggling with this problem for two days.

My development PC is running Windows XP/Office 97. The work stations are
running Windows 2000/Office 97. In the past I have always compile the
Access front end file in the developments PC before letting the staff
copy the access file. Since two days ago, despite the access file is
compiled in my development PC, the client's system complains it is not
compiled. (using IsComplied() function)

I have reinstalled Office 97 in my PC, applied SR1 and SR2b. I have also
decompiled the access file before compiling. It just won't stay compiled
in clients' PC. If I compile the access file using Clients' PC, then I
don't have this problem. I first thought this may be caused by recent
code changes, but I pulled out an old version and compiled, it had the
same problem.:(

So looks like my PC can no longer fully compile access files. There
isn't software change I can recall in my PC, other than automated MS
upgrade.

Any hint you can provide to put me in the right direction?
Thanks.

[dmkeith2]

Hey Mr. Allen Browne what books do I study to get as smart as you about
MS Access?

My list so far includes:

1. MS Access 2000 Bible
2. VBA Developer's HandBook
3. An SQL Book

What else do I need? You and that Steve guy that posts here know your
stuff.

I know time and experience will help, I'm starting a side company
building these MS Access databases, I have enough experience to build a
good database, but I would like to improve on my experience.

Thanks

[Allen Browne]

Thanks for your comments.

Nothing beats experience: trying out what works to find the best way to do
something, and along the way discovering what does NOT work as well. But
much of what I have learned about Access over the last 12 years has come not
just from my own experience but the experiences of everyone else who posts
in these newsgroups as well. You need the good books such as the Access
Developers Handbook by Ken Getz et al (published by Sybex). But you can also
learn heaps about what does and does not work and creative ways to handle
things from the discussions with other Access developers in these groups.
Mind you--if you like helping people--it can get addictive! :-)

--
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.

<dm******@hotmail.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...

Hey Mr. Allen Browne what books do I study to get as smart as you about
MS Access?

My list so far includes:

1. MS Access 2000 Bible
2. VBA Developer's HandBook
3. An SQL Book

What else do I need? You and that Steve guy that posts here know your
stuff.

I know time and experience will help, I'm starting a side company
building these MS Access databases, I have enough experience to build a
good database, but I would like to improve on my experience.

Thanks