Convert Access 2000 to 2013

[Perceptus]

Database Information: One main database with workgroup file and about a dozen front end databases with linked tables to the main database. Current database version is 2000 I believe.



I have done a code review of all the MDB and MDA files I maintain and see no problems afaik. All code recordsets use DAO. What are the other hangups I could encounter when Upgrading to 2013?

[ItsMe]

What sort of problems do you expect to see with DAO? My understanding is this is referenced in the Offfice Database Engine, starting with 2007. The Jet engine is now referred as ACE or replaced by ACE or something. I think ADO may not work in in ways it used to.

[Perceptus]

I do not expect any problems with the DAO references.

[ssanfu]

...One main database with workgroup file.....

I would advise removing the workgroup security before trying to do the conversion. Since MS removed the workgroup option in 2007 (I think it was in ver. 2007), it is safer if you remove the security first.

My $0.02

[Perceptus]

Thank you for that thought Steve. Are there any other idea's?

[Perceptus]

Is the use of MDA files supported in 2013?

I have read that 2013 has no ULS and that I will need to find another solution for this.

[ssanfu]

Don't know about addins in A2013.... don't have it.

I believe ULS was removed in Acc2007.

And, yes, you will need to find another solution for user level security.

[ItsMe]

I haven't tried it but supposedly 2010 will link and or Import with MDA.

I guess there are new ways to lock down your accdb files using the ChangeProperty function. It seems like this should match any functionality you would have got from an MDW file short of going executable. Seems like the best place to call the function is on an AutoExec Macro.

I found some info here, but I have not got to the point of implementation.
https://www.accessforums.net/securit...lbar-3536.html

FWIW