"Tony Toews [MVP]" <ttoews (AT) telusplanet (DOT) net> wrote

This driver DID. After a number of server crashes pointing at that printer,
I did some research and found that it was running at the same lever as the
OS. I removed that drive and waited a few months until a new one was
avialable that ran at the proper level.

"paii, Ron" <none (AT) no (DOT) com> wrote:

Sorry. I'm agreeing with you in that printer drivers can crash OSs as can video
drivers. But I'm disagreeing that apps can crash OSs. Well, unless they have a
memory leak or some such.

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/

On Jan 18, 9:00*pm, "David W. Fenton" <XXXuse... (AT) dfenton (DOT) com.invalid>
wrote:
Still no further forward with this. Whenever I access a form which has
VBA code in OnOpen (or any other event) then Access closes down. I can
open forms which down have any events but they are few and far between!

<jon (AT) norchard (DOT) com> wrote

On Jan 18, 9:00 pm, "David W. Fenton" <XXXuse... (AT) dfenton (DOT) com.invalid>
wrote:
Take a look at Solving Problems with Library References on allenbrown.com
You may need to re-register VBA vba332.dll

Look at "Terminal Services Application Compatibility Notes" at Microsoft

"jon (AT) norchard (DOT) com" <jon (AT) norchard (DOT) com> wrote:

Have you done 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

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/

Joh, we have same problem. Ours is on 2 "servers" and we fixed one.
Maybe this will help.

We have 2 servers BOTH running Windows Server 2003 -r2 (32 bit) - Dev
and Prod. We installed Access 97, 2000/2003 and 2007 on BOTH. Access 97
did not work on EITHER. Upon opening an existing form in display mode,
the form flashes up for a second then Access quits entirely. However the
first TWO forms in North Wind Traders database open fine, when you click
on the first form in the menu, categories, it closes Access.

We found a fix to re-register a DLL (this was 3 months ago and I THINK
it was on the Allen Browne website that referenced vba332.dll - it seems
VB6 had overlaied the proper version so we needed to re-register the one
that came with SR2) - anyway I re-registered the DLL on BOTH boxes and
our DEV box began working. PROD however did not. We tried various things
up to now with no luck.

Ok Jon, if you have not tried it, give it a go if it sounds like
something that might help!

Yesterday I removed all Access 97/Office 97 files, Registry settings as
well as doing an UNINSTALL of OFFICE97. Removed all other versions of
OFFICE as well as manually removing whatever we found leftover that
Office remove did not remove (from a KB article).

I Installed Office 97 full blown and it STILL acts the same way.

Currently I have discovered if I make a copy of a form by the following
approach, it works. Unfortunately we have WAY TO MANY forms across to
many databases to make that an option. This works: open a blank form in
Access 97, then open an existing form (both open in DEV mode) and copy
the contents of the old form (form AND code) and paste into the new
BLANK FORM. When that new form was saved then opened, that newly copied
FORM works fine!

So OLD FORM causes ACCESS 97 to completely quit
Making an EXACT COPY of that FORM as stated above works!

*** Sent via Developersdex http://www.developersdex.com ***