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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Best Practices

Status
Not open for further replies.

testeng

Technical User
Apr 5, 2001
32
US
I am curious if this it the proper way to do this. If in your app you connecting to 2 different DataBases should you create 2 seperate class modules for each DB or just one for the DB that the majority of the app is for and just create a connection in the routines (or just a Public function) for the DB that is not being used as much.

thanks
 

testeng, have you read FAQ222-2244 item 15 yet? Perhaps the whole FAQ222-2244 will be a help to you.

You are asking a very subjective question and the answer depends upon the style of the programmer and the business rules that that they may work under/with.

So with that said you could also create a single class that you instantiate twice. Once for each db if you wanted to.

Once again this depends upon the business rules that you are operating under.

Don't forget to read FAQ222-2244 item 15.

Good Luck

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top