BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
X-WR-TIMEZONE:America/Phoenix
BEGIN:VEVENT
DTSTART:20121019T183000Z
DTEND:20121019T194500Z
SUMMARY;ENCODING=QUOTED-PRINTABLE:The Dangers of Accessing SQL Data - Kevin J. Cully
DESCRIPTION;ENCODING=QUOTED-PRINTABLE:In the 'What is old, is new again' department, Microsoft has announced that the future and preferred data access methodology is ODBC. As FoxPro programmers, we've been accessing SQL data via ODBC for years. But there have been stumbling blocks and some showstoppers over the years. We'll take a look at them and develop an approach to find them before they find us. We'll answer questions such as:=0D=0A=0D=0A
- Do you know whether all of your users are using the same version of the ODBC driver for your database?
=0D=0A- Does VFP behave the way you think it is supposed to when querying against a field type such as TEXT? What about MIDTEXT or LONGTEXT?
=0D=0A- ODBC drivers are famous for fixing an existing bug, and then having the next version it break again, only to have the next version fix it again. Repeat. Should you go with the next version and will your program work?
=0D=0A- What about upgrading to the new version of Microsoft SQL Server? or PostgreSQL? or Firebird? Will your existing SELECTs, INSERTs, UPDATEs and DELETEs behave the way you intend? Was there a deprecated feature that breaks your code?
=0D=0A- What about performance? From one version of ODBC driver to another, we hope that performance improves. What if it gets slower? Much slower? Best to find that out sooner in the development cycle.
=0D=0A
LOCATION;ENCODING=QUOTED-PRINTABLE:Flagstaff
UID:SWFOX20121019T183000Z
PRIORITY:3
END:VEVENT
END:VCALENDAR