I take it that you tecnogeeks are talking about a less expensive option to the SQL set up that we went with? Seems I remember bits and pieces of this conversation...
J.Michael Pontious MD Professor-Family Medicine Program Director-OU/Enid Family Medicine
"Great spirits have always encountered violent resistance from mediocre minds" - Einstein
This electronic message transmission contains information from J.M.Pontious MD which may be confidential or privileged. The information is intended for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents
-----Original Message----- From: Electronic Medical Record - Enid [mailto:[log in to unmask]] On Behalf Of Osburn, Gene (HSC) Sent: Thursday, March 04, 2004 2:56 PM To: [log in to unmask] Subject: Re: MySQL
Jim,
I have finally solved what I think is the last barrier to using MySQL as the database for the program. You have to specify client side cursors for the ODBC driver that MySQL uses. Like the old Access and some old DOA drivers. Data returned from SQL queries were pretty flakey and confusing before I stumbled on this solution.
I have finally solved what I think is the last barrier to using MySQL as the database for the program. You have to specify client side cursors for the ODBC driver that MySQL uses. Like the old Access and some old DOA drivers. Data returned from SQL queries were pretty flakey and confusing before I stumbled on this solution.
