Pitfalls with a 2003 to 2010 file format conversion?

[redbull]

Alright, I have a program that people have been using for awhile, I recently brought everything up to access 2010. Once I did that, I made sure the reference libraries and everything was set correctly, compiled it into a accde file and sent it out into the wild. Everything seems to work.



Now, a few weeks later I am trying to add some code and features to the file. I open up the file and make some changes to it, simple code nothing on load or current (relevant later).

After putting in some code, testing it out in the vba screen I want to save and send this copy of the file out. It saves fine, but then when I try to open the file access crashes. I then attempt to open the file in admin, and it opens fine. I then try to alt+f11 into the code window, and once again it crashes. IF it was faulty code in the load or current modules, I would get crashing when the form automatically opens... but that's not the case.

So I know my code isn't the culprit here, simply because I was able to test it and it does function well and is nearly identical to other code I have in the app. Any ideas? Are there any pitfalls to avoid in 2010 that I am not aware of? Is it time to just scrap vba and attempt to write this in .net?(time permitting of course).

Any who, thanks for the read and any feedback.

--I started rebuilding the program from the last save point. After every step, I saved and closed/opened the file. It seems the adding another button to the form is causing the corruption?

[JrMontgom]

By save you mean compile the code then save the form? I have had problems saving a data base when I had a bug in the code when I compiled it. I had to use the DataBase file/Decompile when I reopened the Access program.

[NTC]

boy I hate to throw this out there - but are you really on XP?....