"ljubo lecic via AccessMonster.com" <fo***@nospam.AccessMonster.com> wrote:
I have written a pretty complex ACCESS accounting aplication which is
working fine.But under some circumstances I get this nasty error message:
"Microsoft ACCESS has encauntered a problem and needs to close ..."
Then I am asked if I will send an error report to Microsoft.
I wonder If I can get the response from Microsoft explaining the reasons of
errors .What is the best way to find an explanation of the error ??
For example: Today, I tried to run my aplication (developed under ACCESS
2002) on the Windows 2000 platform (ACCESS 2003) and when I start the
aplication It sometimes works normally and the other time I get this
message, under same circumstances.
Darn, it would be nice to get a reproducible situation so you can figure out what is
causing the problem. Are you distributing an MDE or MDB on the Windows 2000
platform? What about references? Have you tried a decompile?
Decompile or how to reduce Microsoft Access MDB/MDE size and decrease start-up times
http://www.granite.ab.ca/access/decompile.htm
Does this happen only on startup? Does the Access 2003 system have SP1 installed?
If you go into the event log you should be able to find the error in there. Do you
see anything there like an incident or case number? If so you might be able to
contact MS using that incident or case number and get some more information on the
problem.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm