Access 2003 Crashes on Vista not on XP. Gee, there's a surprise!!

Okay, thanks to all for their input.
Alas, so far nothing works.

I do have a valid printer attached although it's a network printer attached to another pc on the workgroup.
I tried decompiling, recompiling and compacting; no dice.
I get no error messages other than the one that says access has stopped working and is checking for solutions or that I don't have enough memory.  The latter doesn't happen often at all.

I copied the offending form, opened the vb editor and stripped out all the code.
It seemed to work fine better, though when I clicked on a button to open a report it crashed.

Now, out of the clear blue, it has gotten worse.
Now when I open the file, while holding the shift key down, and doing nothing, just let it sit at the Access DB page, it pops an error message that says "file not found".
I click on ok and that box just keeps appearing.   I have to kill the app to get it to close.
When I click on help it shows error 53.
The weird thing is that, before it crashes it's doing NOTHING!!!
I have no forms open.  I've run no reports...

Man, this is getting worse.
Meanwhile, the exact same db works perfectly on XP.

Any further thoughts?
B

A bit more info.
I created a new db.
I imported all the tables, queries, macros etc.
No problem except when importing a few of the forms, one of which was the copy of the main form I created for troubleshooting purposes.
This form has all the VB code stripped out of it, yet it still crashes Access when I try to import it.

This is a really large, complicated form and I'd really rather not rebuild it if I can avoid it.

I was thinking that the underlying relationships between the tables might have gotten corrupted somehow but the query that the form was bound to before I unlinked it runs just fine.

This is really frustrating!!

Thanks again.
Butch

You might be able to copy the large, complicated form in pieces. Highlight, copy a section, paste, repeat.

Is the new db causing the problem(s)?

If you do NOT copy the forms where you have troubles, does the new database work okay?

If so, you can try the undocumented SaveAsText and LoadFrom text:

In the Immediate window, type this:

Application.SaveAsText(acForm, "NameOfYourForm", CurrentProject.Path & "\NameOfYourForm.txt")

and press the Return key. Now delete that form, compact and repair, then open the Immediate window again and type this:

Application.LoadFromText(acForm, "NameOfYourForm", CurrentProject.Path & "\NameOfYourForm.txt")

Access should rebuild this form entirely from text, which can sometimes recover the form from corruption. If not, you'll have rebuild, as Nelson suggests, or import from a recent, known good backup.

Basically I abandoned troubleshooting efforts and upgraded the app.  I would like to award points to those who helped.

I would like to also add that the solutions offered were valid and good.
The fact that EE gave a grade of B in no way reflects the quality of the answers given.