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 of this information is prohibited.  If you received this electronic transmission in error, please notify me immediately by electronic mail.
 
 
 

	-----Original Message----- 
	From: Electronic Medical Record - Enid on behalf of Cacy, Jim R. (HSC) 
	Sent: Thu 3/4/2004 3:13 PM 
	To: [log in to unmask] 
	Cc: 
	Subject: Re: MySQL
	
	

	Cool!
	
	
	-----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 will do some more testing the next couple days, but I think you can
	now run the program with MySQL in instead of M$SQL if you prefer.
	Trapping the backslash escape characters and formating stored dates in
	the YYYY-MM-DD HH:MM:SS format was the easy part.
	
	I have also found some programs which claim they can convert VB 6 code
	to pure Java code. I will check those out soon.
	
	Gene