A2007 gives error message on A2000 db

[froggiebeckie]

Just upgraded my system to Office 2007, as part of an ongoing upgrade for everybody. Until everyone has been upgraded, we'll have some using A2007 and some sill with A2003.
Have a db (A2000 format) that I can't open using A2007. I get "An error occurred while loading Form_Transactions_Form. Do you want to continue?"
If I select Yes, then I get an "Invalid Procedure call or argument."

I've copied the db to a different computer, using A2003 and it opens and works fine.
I can't save the db into the A2007 format until everyone has been upgraded and that may be months from now.

Anybody have any idea on how to correct or work around this?

Thanks for taking the time to look.
BeckieO

 

[the_net_2.0]

open it with the SHIFT key, and bypass the form opening. Look at the code behind the form. Compile the code. You might find the problem with the compilation.

Code is NOT compatible between 2 versions of Access from ANY year to ANY year. MS simply doesn't pay attention to it. So get used to it. From 2000 to 2010, there have been code inconsistencies. I've found them all, some through other people and some by my own accord.

 

[missinglinq]

Also, after opening the database while holding <SHIFT> down (hold it down, start the app and wait until the Database Objects Window appears) you need to check your References.

When apps run fine on one machine and not on another or run fine in one version and not when run under a newer version, one of the first things you have to think about are missing references.

If you haven't looked at this, here are Doug Steele's detailed instructions on how to troubleshoot the problem:

http://www.accessmvp.com/DJSteele/AccessReferenceErrors.html

Code is NOT compatible between 2 versions of Access from ANY year to ANY year.

Sorry, this is simply not true! Sure, there are always glitches with any new versions. And there are some major features that have been added with 2007/2010. But Access has had reliable backward compatibility since v97; in the vast majority of cases code written in earlier versions will run in later versions.

In upgrading, the one thing you do need to pay special attention to are any ActiveX Controls that may have been used, especially things such as Date Pickers. The latest versions of any language tend to have latest versions of these controls, and earlier versions aren't always compatible. That's why experienced Access developers have always considered it best practice not to use them.

Allen Brown has an excellent guide, Converting to Access 2007 or 2010:

http://allenbrowne.com/Access2007.html

Linq ;0)>

 

[boblarson]

Code is NOT compatible between 2 versions of Access from ANY year to ANY year. MS simply doesn't pay attention to it. So get used to it. From 2000 to 2010, there have been code inconsistencies. I've found them all, some through other people and some by my own accord.

That is a very incorrect and broad GENERALIZATION. Code IS compatible between versions and has been very stable since Access 2000. There are version specific code that has been added as the versions go along and some things that have been dropped. But that is a minor subset of VBA and MOST databases will function just fine between versions.

One of the issues is using ActiveX controls. Those are a potential time bomb and not everyone knows that so that is a problem. I found out the hard way a long time ago and have since avoided them like the plague unless I can't do something without one (and that is rare).

But to generalize and say that code isn't compatible between versions is bullsh&@. I've managed to move apps from version to version with no problems whatsover and so have many, many others. But there are issues to address between versions and you will find that with ANY software company.

 

[vbaInet]

... and when a function is deprecated an alternative function is most of the time available. They seem to be better alternatives too.

 

[the_net_2.0]

But to generalize and say that code isn't compatible between versions is bullsh&@.

How many beginners and/or non-informed developers do you come in contact with, Bob? That's a conservative approach, and it's certainly not bullsh&@. When you're dealing with people that don't know what they're doing themselves, it's better to cover all basis, than to have that person come back to you and say you're incompetent.

Yes, inconsistencies are rare, but for 99% of people out there, which obviously is the percentage that DON'T know stuff like this, it's a lot better to give them information that will keep them safe (from themselves and their ignorance), rather than pi$$ them off. (and no, I don't think the OP here is ignorant)

As far as what you typed in this thread, it couldn't be more wrong. But...that is my 2 cents. I will bow out now, and let things get back on track. If you want to debate the theory, you're welcome to send me a PM!

 

[boblarson]

How many beginners and/or non-informed developers do you come in contact with, Bob? That's a conservative approach, and it's certainly not bullsh&@. When you're dealing with people that don't know what they're doing themselves, it's better to cover all basis, than to have that person come back to you and say you're incompetent.

Yes, inconsistencies are rare, but for 99% of people out there, which obviously is the percentage that DON'T know stuff like this, it's a lot better to give them information that will keep them safe, rather than pi$$ them off.

As far as what you typed in this thread, it couldn't be more wrong. But...that is my 2 cents. I will bow out now, and let things get back on track. If you want to debate the theory, you're welcome to send me a PM!

Adam, you've always just been Over The Top when it comes to stating things. Yes, there are exceptions to EVERYTHING and I have come into contact with many, many, many non-developers and just users and such. And I know you don't believe it but the majority of them have never had a problem with moving between versions. I never said there were not problems out there. But your GENERALIZED statement makes it sound that it is a worse problem than it really is. I wish you would just keep your SENSATIONALISM off the board or go somewhere else where you can spout off your insane nonsense.

A lot of times your answers to people are not helpful in the least. I don't know what it is but you tend to get in a mood and then give terse, short, and a lot of times not completely accurate answers.

So, anyway - just avoid generalizing and then others won't call you out on it.

 

[vbaInet]

When you're dealing with people that don't know what they're doing themselves, it's better to cover all basis, than to have that person come back to you and say you're incompetent.

Taking the Consultants approach