DaveT said:
I've tried most of the typical things such as creating new, blank mdb, and
then importing all objects from app; using jet comp utility, etc.
I wouldn't expect JetComp to help in this case as Compact and Repair,
which is what JetComp runs, only cleans up tables and indexes.
Yesterday reinstalled 2003 (from factory CD) on backup machine and applied
updates through SP3 (11.8166.8172), but did not apply hotfix. So far, the app
now seems stable and I can make form design changes without incident.
Glad to hear you have a solution.
Yes, I've sent more "report error to Microsoft" crash reports in the last
week than in the last, oh, five years! This from primary and backup
development machines.
I don't discount the possibility of some issue unique to my development
environment, but this did all start (for me) after installing the hotfix on
two machines.
Microsoft has stated that sometimes they get very interesting crashes.
Many of them. From one particular system. They would love to help out
by displaying a message something like "Call this number and quote
case # 123456. This will be a free support call." Trouble is
privacy rules forbid them from doing this. Can you imagine someone
getting this message and freaking out yelling to the world "Microsoft
are spying on me!!!"
I should see what the rules are on support calls for a problem where a
hotfix is causing the problem. That is will the support call be free.
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
Tony's Microsoft Access Blog -
http://msmvps.com/blogs/access/