Split Database...
If I split my database into a backend/frontend scenario do all the users who will be using the frontend need to have Access installed on their machines?
NG,
NG,
Tracy
Yes, they still need access on their machines.
Unless you install the FE on each users system using the Access Runtime ...
mx
mx
ASKER
mx,
Can you elaborate a little on your suggestion.
Thanks,
Can you elaborate a little on your suggestion.
Thanks,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I assume they aren't backwards compatible..?
What version of Access are you using ?
mx
mx
nike_golf,
I have used Access 2007 and 2010 with JET4 database created with Access 2000-2003. Both the MDB and MDE formats.
I have several clients that use the Access 2007 (full and runtime) to run my Access 2003 MDE front ends. Access 2007 and 2010 seam to be less forgiving about doing things incorrect. I have had very few things that I have had to tweak to get the MDE to work in Access 2003/2007/2010 runtimes.
I have a few new client with databases that someone else created with Access 2000. The databases ran fine with Access 2000. The databases had lots of issues running under Access 2007. I have learned that Access 2000 allowed some events to work in forms that really should not really have worked. The newer versions have corrected this issue.
In theory Access 2007/2010 runtime should run your older database. Tghis appear to be true only if design correctly.
I assume they aren't backwards compatible..?
I have used Access 2007 and 2010 with JET4 database created with Access 2000-2003. Both the MDB and MDE formats.
I have several clients that use the Access 2007 (full and runtime) to run my Access 2003 MDE front ends. Access 2007 and 2010 seam to be less forgiving about doing things incorrect. I have had very few things that I have had to tweak to get the MDE to work in Access 2003/2007/2010 runtimes.
I have a few new client with databases that someone else created with Access 2000. The databases ran fine with Access 2000. The databases had lots of issues running under Access 2007. I have learned that Access 2000 allowed some events to work in forms that really should not really have worked. The newer versions have corrected this issue.
In theory Access 2007/2010 runtime should run your older database. Tghis appear to be true only if design correctly.
Related topic - no points please:
Now that you're split, you're welcome to use our free J Street Access Relinker on our J Street Downloads page: http://ow.ly/M56Q It's a lot nicer than the Linked Table Manager.
It's some simple code that you copy into your front-end application. It handles multiple Access back-end databases, ignores non-Access tables, and can automatically and silently relink to back-end databases in the same folder as the application (handy for work databases or single-user scenarios). There's a ReadMe table with instructions.
Cheers,
Armen
Now that you're split, you're welcome to use our free J Street Access Relinker on our J Street Downloads page: http://ow.ly/M56Q It's a lot nicer than the Linked Table Manager.
It's some simple code that you copy into your front-end application. It handles multiple Access back-end databases, ignores non-Access tables, and can automatically and silently relink to back-end databases in the same folder as the application (handy for work databases or single-user scenarios). There's a ReadMe table with instructions.
Cheers,
Armen
ASKER
Don't worry no points are coming your way... Just abuses that your breaking the rules of experts by advertising.. I'll send them a note and ask.
TheHiTechCoach, I'm running 2003. So, if I split it and download the 2007 runtimes I can use the frontend on a machine without access installed?
Any restrictions that you know of when designing the frontend?
TheHiTechCoach, I'm running 2003. So, if I split it and download the 2007 runtimes I can use the frontend on a machine without access installed?
Any restrictions that you know of when designing the frontend?
"Don't worry no points are coming your way... Just abuses that your breaking the rules of experts by advertising.."
nike_golf:
Armen is in no way breaking any rules. He is offering you a *free* automatic relinking tool ... note the word free:
"you're welcome to use our free J Street Access Relinker on our J Street "
There was *no* need for you to hit the Request Attention button and waste the mods time!
mx
nike_golf:
Armen is in no way breaking any rules. He is offering you a *free* automatic relinking tool ... note the word free:
"you're welcome to use our free J Street Access Relinker on our J Street "
There was *no* need for you to hit the Request Attention button and waste the mods time!
mx
"So, if I split it and download the 2007 runtimes I can use the frontend on a machine without access installed?"
Yes.
At this point, your original question has been answered.
mx
Yes.
At this point, your original question has been answered.
mx
nike_golf:,
You can not use an Access Front End with Access installed. There is no way around it.
For PC's that do do not have a purchased license for the full.retail version of Access, you can install the Access Runtime version.
Think of it similar to a PDF. You have to have some software installed to view the file.
Example:
1) You have to have the full Adobe Acrobat to create a PDF. Jjust like you need the full version of Access to create a database. The Full versions will also view their files
2) To view a PDF you only need the Adobe Acrobat Viewer. You can not create a PDF with the viewer. Similar, you can use the Access runtime to "view" a database and enter data. You just can't create a new database or any new objects since the designer functionality is turned off.
You could think of the Access Runtime as Access in "viewer" mode.
Not an accurate statement..
So, if I split it and download the 2007 runtimes I can use the frontend on a machine without access installed?
You can not use an Access Front End with Access installed. There is no way around it.
For PC's that do do not have a purchased license for the full.retail version of Access, you can install the Access Runtime version.
Think of it similar to a PDF. You have to have some software installed to view the file.
Example:
1) You have to have the full Adobe Acrobat to create a PDF. Jjust like you need the full version of Access to create a database. The Full versions will also view their files
2) To view a PDF you only need the Adobe Acrobat Viewer. You can not create a PDF with the viewer. Similar, you can use the Access runtime to "view" a database and enter data. You just can't create a new database or any new objects since the designer functionality is turned off.
You could think of the Access Runtime as Access in "viewer" mode.
And I meant with the Access Runtime ..
mx
mx
Thanks for jumping in, mx.
Every Access database should be split. Period. But linking and relinking Access tables is a prevalent problem. I've seen it done badly so many times, and that hurts the perception of Access in general. That's why I often suggest our free Relinker utility. Use it or don't, as you wish. But yes, it's free. As are all our other downloads.
Cheers,
Armen
Every Access database should be split. Period. But linking and relinking Access tables is a prevalent problem. I've seen it done badly so many times, and that hurts the perception of Access in general. That's why I often suggest our free Relinker utility. Use it or don't, as you wish. But yes, it's free. As are all our other downloads.
Cheers,
Armen
modus_operandi,
Thank you for the clarification.