I’m probably making some incorrect assumptions leading to incorrect conclusions, so I’ve set out what I ASSUME is right and my conclusion – but you chaps will know better.
Assumption
I read somewhere that Access Runtime is like a database viewer. It is similar to the Adobe Acrobat Reader. Acrobat Reader will open a PDF. It will not allow you to create a PDF. Similarly Access Runtime is to “view” a database.
Conclusion
If my user copies my FE & BE to his computer, (with Access installed), he will be able to use ("view") the Application.
If Access is not installed, there will be an error message and I can advise the User to to download Access Runtime for free from somewhere (not sure where yet. Will 2007 Runtime do?).
Next Assumption
The FE will not be linked to the BE.
Conclusion
I just tell the User how to use the Linked Table Manger to refresh the links. – not pretty but effective methinks.
Does that work?
Perhaps what I am really asking is, Do I really need all the developer tools and wizzy background linking stuff - can this be done on the fly?
Assumption
I read somewhere that Access Runtime is like a database viewer. It is similar to the Adobe Acrobat Reader. Acrobat Reader will open a PDF. It will not allow you to create a PDF. Similarly Access Runtime is to “view” a database.
Conclusion
If my user copies my FE & BE to his computer, (with Access installed), he will be able to use ("view") the Application.
If Access is not installed, there will be an error message and I can advise the User to to download Access Runtime for free from somewhere (not sure where yet. Will 2007 Runtime do?).
Next Assumption
The FE will not be linked to the BE.
Conclusion
I just tell the User how to use the Linked Table Manger to refresh the links. – not pretty but effective methinks.
Does that work?
Perhaps what I am really asking is, Do I really need all the developer tools and wizzy background linking stuff - can this be done on the fly?