It's always SOMETHING !

dcavaiani

Registered User.
Local time
Today, 15:23
Joined
May 26, 2014
Messages
385
We are moving a 2002 .mdb to 2016 .accdb. I am the developer and it is all working fine on my laptop. I have sent a copy of the database to my user, and he is having an error msg come up with a Macro which loads a form with a SUBMIT button, which executes a series of embedded macros, etc. and the following error msg comes up ... ??? IMG_0012.jpg
 
Looks like you were using the old ActiveX calendar. It's been removed in later versions of Access in favor of a built-in calendar. In 2016, all Textbox bound to a date field automatically displays a popup calendar.
 
If you need a calendar control you can search this forum, there are a lot of "roll your own" that work well.
 
Looks like you were using the old ActiveX calendar. It's been removed in later versions of Access in favor of a built-in calendar. In 2016, all Textbox bound to a date field automatically displays a popup calendar.

I agree, but why works on my Laptop and an error msg on my user's PC - on which 2016 was just installed ??? It is the same database which I just sent him ??
 
Your laptop probably still has the ActiveX component (DLL) installed; whereas, it's probably missing on the other computer. Just a guess... What version of Access are you using on your laptop?
 
Your laptop probably still has the ActiveX component (DLL) installed; whereas, it's probably missing on the other computer. Just a guess... What version of Access are you using on your laptop?

2016 on each - my laptop also has a 2002 version installed, and 2016 on my user's PC which was just installed and he had a 2000 version which is now removed - what do we need to check ??
 
Go to the VBE window and go to Tools > References to see if any are marked as "MISSING."
 
Try hitting the Alt+F11 key combo.
 
Ok I see that. It is gonna be a while b/4 I can get my user to do the same. I assume that we should each have the SAME ones checked !

Either that or find where in your database you are using the calendar and remove it.
 
Either that or find where in your database you are using the calendar and remove it.

I did find every possible use of old calendars in the 2002 database and removed all the references and it all works fine on my laptop, then that whole altered and fine running with no errors .accdb was sent to my remote user who had just installed the 2016 on and then that error msg somehow comes up ...
 
Other user may have to compact/repair or even decompile - assuming you didn't miss anything.
 
I may have found it. I ran the documenter against forms only and got 2 error msgs for forms that still had the old calendar control in them. I fixed those 2 and resent the database to the user. We'll know soon ...
 

Users who are viewing this thread

Back
Top Bottom