I also enjoy immensly the freedom that Oterro and VB give me. Multiple connections are a breeze. As in everything else in object oriented programming, one needs to make sure that connections are properly dropped before exiting the program. I leave my connections open at all times. That way there is no time delay when I want to access a database.
The business object classes that we use at SQLResources are designed to almost totally insulate the user from the details of the backend. I can instantiate a business object and pass it a reference to a connection and it handles all the details. Each instance of a business object can work with one table, or view, in any ODBC database. I hope someday to see a Client-Server version of R:Base. That would be awesome. -- Dennis McGrath mailto:[EMAIL PROTECTED] -- Tools for R:BASE programmers http://www.enteract.com/~mcgrath/dennis -- Full time consultant with SQL Resources mailto:[EMAIL PROTECTED] ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
