At 10:26 PM -0500 17/7/06, C. Wyatt wrote:
[EMAIL PROTECTED] wrote:
I feel incredibly out of it, but I am still not getting it. Suppose
I write a program in Real Basic, and when it runs the app opens a
MySQL database via plugin, does that mean I am needing to bundle
MySQL or that I need SQL to run? Or and I just using the file
format of a MySQL database via Real Basic and never actually
opening the database via another tool is that not requiring a
license?
MySQL informed us that our application did not require the license
if it supported multiple databases. In other words, though we
support MySQL, we leave it to the client to decide if MySQL or
SQLite is the database. I would like to have pg support, but I fear
clients located in other cities will not locate anyone with pg
experience. MySQL is the gorilla with tons of books and training out
there.
I'm not sure how I would deal with this if I had a wildly popular
application. I like MySQL, especially since you can change the
engine and new engines are in development. If you can support pg,
the existence of a fast commercial RB plug-in is a selling point.
There is no "right" answer to this. If your clients use MySQL and
own it, they probably don't want to mix-n-match systems. The nice
thing about using an ODBC solution is that the backend is less your
problem that the client's problem.
Heh?? Ever tried to support a number of different backend systems via
ODBC from different Client OS's?
I have since MacOS 7 and Win95.
Talk about debug everything, everywhere, especially with the old RB
ODBC plugin. Now I avoid ODBC options as much as possible.
--
Cheers,
Dr Gerard Hammond
MacSOS Solutions, 505/176 Glenmore Rd, Paddington, NSW, Australia
[EMAIL PROTECTED] 0414 796 709 http://www.macsos.com.au
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
