Access 03 to Access 13 migration

JohnPapa said:
It appears that the .accdb requires the .mdw and the .accde does not!!!
Click to expand...

Perhaps that is a research gem, JohnPapa. Bravo!
 
Question: Does your VBA actually work in A 2013?
Question: What OS are you using for A2013?

My new HP Phonex computer is scheduled to arrive this afternoon (was expecting last week) if I am home in time to sign for it.
My MAPS subscription from Microsoft has the new versions ready to download.

My struggle at this point is how to set up the generic Windows 8 OS to behave like the Microsoft presentation. His Surface had a VM to allow a full SQL Server installation to run in parallel to the MS Access 2013. It is going to be imporatnt to me to have SQL Server, Sharepoint Server, Access 2010 and Access 2013 running for development.

The OS setups are not my speciality. Finding a site to describe the steps just seems to elude me. If anyone has suggestions on steps to set up a Windows 8 Enterprise with the VM for the SQL Server - please let me know.

I might not catch up with your Access 2013 migration for another week, but look forward to helping with this kind of thing.
 
fil properly in the first place

This can be tested by pointing the Open Command Line at the default MDW and see if it opens. I would think that it will work. The difference is that the users should be missing. Also testing on a separate maching will help prove the point.

EDIT
I made a mistake with my copy paste.
End Edit

I would guess that the MDW was not set up properly in the first place.

This can be tested by pointing the Open Command Line at the default MDW and see if it opens. I would think that it will work. The difference is that the user privlidges should be missing. Also testing on a separate machine will help prove the point.

If this is correct then ignore the MDW all together as it does little.
 
Last edited:
Unfortunately it seems that Rainlover is correct

PHP: 
I don't see that your code is doing anthing except forcing the file to open in Version 15.

It seems that even though the MDB was saved as ACCDB, the link to the MDW still remains. For full compliance and operation under A13 the MDW link needs to be removed together with the User Level Security that A13 does not support. I bumped into this article for doing just that

PHP: 
http://office.microsoft.com/en-us/access-help/remove-user-level-security-mdb-HP005188240.aspx

To summarize we would remove the ULS from the FE and BE MDBs as per the article above. This would render the MDBs without security, so there would be no need for the specific MDW. I will try and let you know.

Rainlover, if you have something else, some other instructions please post.

Thanks,
John
 
JohnPapa said:
It seems that even though the MDB was saved as ACCDB, the link to the MDW still remains.
Click to expand...

One of the links I posted to this thread made it sound that way as well.... that you could upgrade from MDB --> ACCDB and retain the MDW file, but you could not create a new ACCDB requiring a MDW.

JohnPapa said:
For full compliance and operation under A13 the MDW link needs to be removed together with the User Level Security that A13 does not support. I bumped into this article for doing just that
Click to expand...

But I thought you needed User Level Security? Thus I shared the link suggesting it could be retained.

:confused: (shrug)

Maybe use a scheme like my UPDATE where ID / TIMESTAMP match and totally avoid the need for User Level Security? That is working marvelously for my application... so much better than my databases of nearly 20 years ago.
 
Thanks Michael,

At this point time the goal is to to convert a A03 application to A13 and have it behave as a true A13 application. User Level Security is the next step, but we have to get over the first hurdle.

It seems that you can run a A03 from A13, BUT at some point in the future MS might decide to stop supporting some of the features in A03 and then you would be forced to make the transition. Hence the interest in considering the migration.

John
 
Joan Wild wrote the best acticle but I can't find it. This is strange.

Try your way then if that does not work try the following which is from Memory of several years ago.

Create a Blank New DB in A 2003.

Open this file using the MDW switch you have been previously using for the Current secured DataBase.

Once open try an import of ALL tables (Not Links), Queries, Forms Modules Reports etc.

Then do a Compact and Repair.

Open the new DB without the switch.

There are other ways which you can find via Google but some of these are a little confusing at times.

There is just one more though. Can you open the Current DB in A 2003 without using the secure MDW of even the default MDW. Also try this on another machine.

Post back when you have more to report. I am going Bush next week and will be hard to track down. Just be patient I will get back back some how.

I am due back by the week end.

EDIT

A tidy up of spelling and grammar.
 
Last edited:
Much appreciated Rainlover,

In other words,
1) Remove all ULS from both FE and BE so there will be no need for the MDW that was used so far.
2) Try to convert the FE and BE MDBs to ACCDBs in A13.

Will keep you posted and have fun.
John
 
JohnPapa said:
Much appreciated Rainlover,

In other words,
1) Remove all ULS from both FE and BE so there will be no need for the MDW that was used so far.
2) Try to convert the FE and BE MDBs to ACCDBs in A13.

Will keep you posted and have fun.
John
Click to expand...

John it is more of a case of removing the Objects from the Security rather than removing the security from the objects.

BTW Going Bush is work. It is just a totally different environment with very friendly people.
 
Rainlover,

To remove ULS,

1) Grant full permissions to the Users group and the Admin user account.
2) Put the Admin user back in the Admins group
3) Remove the password from the Admin user.

John
 
I believe I’ve managed to proceed with the migration from Access 2003 to Access 2013 and would like to list the various steps. Please feel free to provide any feedback or corrections.

In Access 2003 I had 3 files FE.mdb, BE.mdb and Secu.mdw
1) Log in FE.mdb, BE.mdb with an account that has Administrator rights.
2) Grant full permissions to the Users group and the Admin user.
3) In my case my vba had (code) references to the Secu.mdw so I had to modify the vba to remove these code references.
4) Create two blank dbs FECopy.mdb and BECopy.mdb.
5) Copy all objects from FE.mdb into FECopy.mdb and from BE.mdb to BECopy.mdb. Make sure that Relationships and other features are selected. It was only until I did this copy that all mention to Secu.mdw was removed. To check, connect to the general System.mdw. Specify internally for FECopy.mdb and BECopy.mdb.
6) Compact and Repair FECopy.mdb and BECopy.mdb.
7) Invoke software without using parameter / wrkgrp and using /user admin.
8) Check that the Library References are correct in FECopy.mdb and BECopy.mdb and add any missing References.
9) Open Access 2013, open FECopy.mdb and save as FECopy.accdb, open BECopy.mdb and save as BECopy.accdb,
10) Link linked tables in FECopy.accdb to BECopy.accdb.

If I missed anything please let me know,
John
 
JohnPapa said:
I believe I’ve managed to proceed with the migration from Access 2003 to Access 2013 and would like to list the various steps. Please feel free to provide any feedback or corrections.

In Access 2003 I had 3 files FE.mdb, BE.mdb and Secu.mdw
1) Log in FE.mdb, BE.mdb with an account that has Administrator rights.
2) Grant full permissions to the Users group and the Admin user.
3) In my case my vba had (code) references to the Secu.mdw so I had to modify the vba to remove these code references.
4) Create two blank dbs FECopy.mdb and BECopy.mdb.
5) Copy all objects from FE.mdb into FECopy.mdb and from BE.mdb to BECopy.mdb. Make sure that Relationships and other features are selected. It was only until I did this copy that all mention to Secu.mdw was removed. To check, connect to the general System.mdw. Specify internally for FECopy.mdb and BECopy.mdb.
6) Compact and Repair FECopy.mdb and BECopy.mdb.
7) Invoke software without using parameter / wrkgrp and using /user admin.
8) Check that the Library References are correct in FECopy.mdb and BECopy.mdb and add any missing References.
9) Open Access 2013, open FECopy.mdb and save as FECopy.accdb, open BECopy.mdb and save as BECopy.accdb,
10) Link linked tables in FECopy.accdb to BECopy.accdb.

If I missed anything please let me know,
John
Click to expand...

This will take some thinking. I might even refer to one of my books.

I feel that something is wrong. I appears too simple.

I assume you want to test this to know for sure don't you?
 
PHP: 
I feel that something is wrong. I appears too simple.

It would be simple if all you needed to do was open the A2003 files in A2013 and everything was done for you.

I have the FE and BE .accdb files, now working under A2013. Is there anything I could do to confirm that the migration worked?

John
 
JohnPapa said:
I have the FE and BE .accdb files, now working under A2013.
Click to expand...

Wow!!! Bravo JohnPapa!!! :D

JohnPapa said:
Is there anything I could do to confirm that the migration worked?
Click to expand...

Do you have a test suite developed to exercise all parts of the application?

I have observed no ill consequences running my A2007 application on A2010. "Plop, plop, fizz, fizz" it just works. In my case I deploy the A2007 DB file to A2010 machines even.

Oh, did you evaluate my decompile script / instructions in A2013 context?
 
Rainlover, as a further test I renamed the two .mdw files that were used, the first contained the permissions and the second is the general .mdw which comes with A2003. The software works, indicating that the .mdw is not being used.


Michael, what does the decompile script / instructions in A2013 do? How should I test it?

John
 
Last edited:
JohnPapa said:
Michael, what does the decompile script / instructions in A2013 do?
Click to expand...

I was referring to this post...

mdlueck said:
For this step...

NT Command Script and Documented Steps to Decompile / Compact / Compile an Access DB
http://www.access-programmers.co.uk...to_Decompile_/_Compact_/_Compile_an_Access_DB

See if the steps are still correct for A2013 please.
Click to expand...

It squishes the DB down to its smallest size, and eliminates problems such as ghost break points in VBA and other Access nonsense.

I run this after I clean up left over objects from the DB file. I am brutal in my cleanup... for example all QueryDef's are created on-the-fly in code, so I delete all traces of QueryDef's, Views, Procedures... EVERYTHING! :D

VBA to Cleanup A2007 DB Extra Objects
http://www.access-programmers.co.uk/forums/showthread.php?t=226466

Perhaps run on a BACKUP copy of your database first!

JohnPapa said:
How should I test it?
Click to expand...

If you have no standardized test suite for your application, then I would just exercise the application as much as possible, trying to be sure to validate ALL functionality.

For applications at my present client which touch anything to do with production, validation / regression testing is required. I must sign off that I performed my documented test suite, and all tests (whether pass / fail) completed as expected.
 
Last edited:
I have been kept out of the system for a while so I have not been able to reply. I think Jon may be doing some work. Anyway back now.

I have read your notations and some things are incorrect but make no difference to the end result so move on.

I have said it before but I do not believe that the security was set up fully in the first place. If Admin was still the owner then it was not set up correctly. In fact I believe Admin should have been removed completly. I would need to research that to be 100% sure.This really does not matter if things are correct now.

To test I would suggest the following.

A Copy of the secured Database. (A)
A Copy of the new unsecured Database. (B)
A copy of any other unsecured Database. (C) All of which are A2003.
Also another Computer with A2003.

Try to open with a Double Click or Select File and press enter. Do not use any switches.

On the First machine one would expect the following.

Without any switches.

A. Does not open.
B. Opens
C. Opens

Using Switches.

A. Opens.
B. Opens
C. Opens

On the Second machine one would expect the same.

Without any switches.

A. Does not open.
B. Opens
C. Opens

Using Switches.

A. Opens.
B. Opens
C. Opens

If you could do these tests we should be able to analise the results.
 
You must log in or register to reply here.

Similar threads

Charax
Error Installing SSMA
Replies
16
Views
677
Pat Hartman
P
P
msoadfsb.exe - Application Error
Replies
8
Views
579
Gasman
Gasman
I
MYSQL Connection on AWS
Replies
6
Views
496
cheekybuddha
cheekybuddha
A
MS ACCESS connect to SQL server BE: Authentication Prompt every time I attempt to
Replies
4
Views
477
GPGeorge
GPGeorge
M
Solved Access VBA ways to obtain file system directory listing
2
Replies
31
Views
1,542
Isaac
Isaac

Users who are viewing this thread

Total: 1 (members: 0, guests: 1)
Back
Top Bottom