Split Database

[Guest]

In the case of a split database, will problems arise if different references
are chosen for the back end and front end.

Thanks

 

[Arvin Meyer]

There shouldn't be any references chosen on the back end. References are for
code and all code resides on the front end.

Under rare circumstances, you could have some code running on the back-end
to do an update. For the most part, it's just as easy to reference the
back-end from the front-end anyway (Like: Set db =
"F:\MyBackendPath\Data.mdb")
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

 

[Guest]

Thank you very much!

 

[Guest]

I removed 3 of the 5 references in the back end, but could not remove the VB
ref and the object library ref. Help tells me to remove the form that is
using the references. But there are only tables in the back end. Any
suggestions?

 

[John Vinson]

In the case of a split database, will problems arise if different references
are chosen for the back end and front end.

No. The references in the backend will never be used and never cause
any problems, so long as you have no code in the back end. Just leave
them be.

John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps