Old Access Database Conversion

[Welshgasman]

I have never ever used db.close?
Does it exist?, if so feel free to use it, instead of nitpicking.

[Micron]

I have never done so because to me, that would imply that I want to close the current db. Probably not a good idea if you could.

[isladogs]

I suggest you try this for yourself to answer the question.
If you think it through, if db.Close did work then any subsequent code such as Set db = Nothing wouldn't run

[Micron]

I can say that it doesn't work from the immediate window, yet it is an intellisense option. Doesn't work as a code snippet either.
M$ documentation says CurrentDb is a method. If a method can have a method (Close) then that's a new one on me.

[Cosimo]

Hi Everybody, it's me again.

After experimenting with converting my old Access database (which I began using Access 2.0 and eventually converted to Access 2003 format), I installed and used Access 2007 to convert it from mdb to accdb.

I discovered some things that needed fixing (thanks to everyone for their help).

I then returned to my original mdb file, and using Access 2003, made those changes (as far as could be done).

I then restored my hard drive to the state it was in before installing Access 2007, so that I could install Access 2016 without any earlier version of Access on my hard disc to cause any conflicts.

Now, with Access 2016 on my PC, I did a fresh conversion of my mdb database to accdb.

I converted the front and and back ends both (the front end has forms, code modules, queries, reports, etc. while the back end has only tables and a few queries, but no code modules).

When converting the front and back ends, I was greeted with a number of pop up messages during the process and at the completion of the process.

The popups displayed the following messages (the first one appeared twice):

"The active content in this file is blocked. Review your trust center settings or contact your IT administrator."


Followed by ...


"This database has been upgraded to the Access 2007 file format. The new database cannot be shared with users of Access 2003 or earlier versions."

The above series of messages occurred during the conversion of both the front and back end databases.


While the last of the two above messages seems to indicate the conversions were successful, I'm not sure what to make of the first message, which sounds ominous.

Is that message, "The active content in this file is blocked. Review your trust center settings or contact your IT administrator." anything for me to worry about?

I don't have an IT administrator. It's just me.

[June7]

What happens when you open the converted db? Do you get security warning?
Review https://support.microsoft.com/en-us/...4-81bb0fcda8a4

[Cosimo]

I think the security warning related to a macro that I set to run when the database is first opened. This macro automatically opens a certain form every time I open the database. I have clicked the button that tells Access it's safe to proceed, and everything seems to be OK now.

[Welshgasman]

You can set a form to open in options. No need for an auto exec macro.

[Cosimo]

You can set a form to open in options. No need for an auto exec macro.

Thank you.

I will do that.

I had a feeling there was a new way to do it.

[Welshgasman]

Thank you.

I will do that.

I had a feeling there was a new way to do it.

Been there since the 2007 version.