Upgrade MDB to accdb using RunTime environment

[ItsMe]

Does anyone have experience using .accdb files in a runtime environment? I need to upgrade from 2003 MDB to 2010 .accdb



My question is, "Will an .accdb FE file link to an MDB backend without any hitches?" I would use the 2010 RT to run the .accdb file on the client. I don’t have to worry about security right now. I just want to begin testing and I was considering this configuration as a testing environment.

The MDB back end does not have to be live. I may consider a hybrid approach in a live environment at a later date. I have several modules that need to be upgraded. So I was wondering if I could work the bugs out, one module at a time. Get one ready and go live with it. Let the users sorta Beta version the thing while I work on upgrading a second module.

Please advise me of any reckless ideas I may have here. Maybe there is a "Best Practice" methodology to this I am not considering, due to ignorance.

[June7]

I've never used runtime so can't address that.

I do link accdb to mdb without hitches (the reverse is not possible).

[ItsMe]

I've never used runtime so can't address that.

I do link accdb to mdb without hitches (the reverse is not possible).

This is good information to know. I can work with a copy of the back end and if I need to, I can make adjustments to the tables on the live BE as I go.

I understand you can test an .accdb file to see what it looks like in runtime by changing the file extension. Changing your existing .accdb file to .accdr will cause it to behave as if in runtime. Maybe I will give it a try at some point with linked tables to an mdb