Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Best practices for using linked tables in split applications

Status
Not open for further replies.

Pack10

Programmer
Feb 3, 2010
495
US
I have a new app which will be deployed to the users soon.
It is a split db. What is the best approach for development and production support. Should I have 2 versions, 1 that is linked to the production back end, and 1 test which will be linked to a test back-end. Or 1 version that I simply go back and forth with the linked table manager. It seems that having the two apps is the best way.....
 
Personally i prefer 2 backends a production and a test just in case during further development i should get an undesired result :) like a corrupt backend. the last thing you want is to have to fix a backend issue that you created for your end users

HTH << MaZeWorX >> "I have not failed I have only found ten thousand ways that don't work
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top