Accde works on my computer only

[eka24]

Please when I create accde and opens it on another computer, it gives error message "upgrade your microsoft access database to the current one, then open the database".
However, when I create the accde on that other machine it works.
what am i doing wrong as both machines are using access 2013.

 

[isladogs]

Your computer may have a later version of A2013 with new or changed features which you may have used in your database

 

[eka24]

OK I will check

 

[The_Doc_Man]

There is also the possibility of reference issues since the references are part of the registry and that is unique to each system.

 

[eka24]

Please in this case what do I do the references

 

[moke123]

What Doc is suggesting is that you check to be sure both machines have the same reference libraries.
heres a link to get you started
https://msdn.microsoft.com/en-us/vba/language-reference-vba/articles/check-or-add-an-object-library-reference

 

[CJ_London]

other possibility is that one machine is using 32bit access/office and the other is 64bit access/office

 

[isladogs]

I deliberately didn't mention either of the other suggestions made by the Doc & CJ London as these would show different error messages

a) 32/64 bit issues are notified with this message

Or using ACCDE files you would get a message like this

b) Reference issues would normally trigger a message similar to this

I may be wrong but I still think the most likely explanation is that a feature added in a later version of A2013 (especially if its Office 365) was used in this database. If so updating the target PC should fix it ... or modify the database so the new feature isn't used.

A typical example is the use of the bigint datatype though that particular change was introduced in later versions of A2016 (Office 365). In that case I believe the message tells you the minimum Access version needed to use that datatype

Hopefully the OP will return & let us know the cause

 

[eka24]

Thanks all for your contribution. I am considering all your points. I must add that for accdb is fine. It's only when I convert to accde that I am unable to open in another machine.

 

[The_Doc_Man]

As a test, port the developer copy of the .ACCDB to a machine that has the .ACCDE problem and try to compile and then open the .ACCDB file there. See if you get any compile errors starting from the DB.

NOTE: This is a suggestion for a type of test that will eliminate certain classes of errors - or find them. If there is no problem with creating the DE file and running it on another system, see if that DE file will then open on YOUR system. This is basically looking for differences between the two machines and it will either show nothing or will toss an error your way. Our suggestions might then differ based on the results.

On the other hand, that error message tells me that you might have a licensing issue, though I'm at a loss to know how the DE file would know. By any chance did you try to include some kind of license API call in your own code, intending to eventually market the app using the Windows Licensing features? From your description, we can't tell much about your work environment so can't guess which way you were going with this app.

 

[eka24]

Doc Man, you are right it is not licensed. As to Api calls that you talk about, am quite new and therefore have no idea. I guess the license might be the problem as you suggested. Thanks I will work on that.

 

[The_Doc_Man]

If the failing machine ALSO has a licensed copy of Access, you will probably not get very far investigating the license. To the best of my knowledge, it is not possible to easily decipher a license due to encryption, and I have not run into cases where there was a difference in licensing between two copies of Access for the same version. I.e. if both machines are running Ac2013, the effect of their licenses should be indistinguishable. But there MIGHT be differences in the options used when Access was installed on each machine, because as I recall, you have at least a couple of dozen "feature" options for an Access installation.

 

[isladogs]

Doc Man, you are right it is not licensed. As to Api calls that you talk about, am quite new and therefore have no idea. I guess the license might be the problem as you suggested. Thanks I will work on that.

I have to say I'm totally baffled by the licensing issue that's been raised.
What exactly isn't licensed?
Do you mean you are using a 30 day trial version of Access?
It can't be a runtime version as that can't create ACCDE files.

Have you checked the version number of Access on each machine?
If they are different, which is newer?

 

[The_Doc_Man]

"upgrade your microsoft access database to the current one, then open the database"

I have to say I'm totally baffled by the licensing issue that's been raised.

I didn't think for a minute that the app was licensed but that message makes me wonder how the second machine knows there was a difference between two different versions of Ac2013. Some kind of licensing would have conveyed that info. OK, the code can look up the "build number" I suppose, but I've never seen that message pop up when two different machines both have Ac2013. Normally that just doesn't happen, given that automatic MS updates to Office might occur unevenly in a multi-system site. If both versions of Access are properly installed and licensed (not talking about the app), the message would be related to Access versions.

The only other way I could imagine this is if someone took a pre-Ac2003 .MDB file and just renamed it to .ACCDB, but if both machines are Ac2013, that doesn't make sense either. So I am still scrambling for explanations, even some that are unlikely. If my little excursion down the garden path confused you, sorry. It's just that confusion, like misery, likes company.

 

[mnaeem2k]

Hi,

I am using access 2010 under windows 10. I have made a simple form using 5 list boxes, 2 buttons, 2 reports from 2 tables. The accde created runs smoothly on my machine.

But get attached error while running on machine under win7.

I believe I have removed all the dead code from the file.
Thank you.

 

[CJ_London]

you are hijacking an old(ish) thread. Recommend you start your own thread. Also if you want responses, you will need to provide more information like what the code is that is failing.

 

[The_Doc_Man]

mnaeem2k, you are new to the forums. This is the type of post that should have its own thread, and they are easy to create. For future reference, please consider that if you have a new problem, it (and you) deserve the response that comes from having a separate thread for it.

OK, that error tells me that whatever you have for the OnClick event, something is wrong with it. Depending on the type of control, you have some choices for an OnClick property. You can name an existing macro; you can write a procedure to be executed; or you can use the [Event Procedure] choice so that the form calls your event procedure when the event occurs.

If you use a specific common event procedure that you wrote, the procedure has to be "visible" to the code that will call it, which means it is either in the form's Class Module or it is a Public Sub in a general module. In this case, assure that you spelled the name correctly in the OnClick event slot and assure that it is visible.

If you have a named macro that does what you want, you can name the macro and it will be executed. Again, assure that you spelled the name correctly in the event slot.

If you use the "standard" [Event Procedure] option, there will be a Private Sub entry point in your class module with the name of the control and OnClick, as for example, MyButton_OnClick. You put your code in that routine and assure that you don't have an error in the code that causes a machine or system fault.

Since you are seeing an error based on differences between the O/S (7 vs. 10), the question is: What do you call from the particular control's OnClick event? It is possible that the correct way to run this is to make the ACCDE file on the Win7 system and then run it on the Win10 system, because Windows apps don't downgrade very well.