Excellent! This looks like it should work.
Another useful reference is
http://lists.mysql.com/cgi-ez/ezmlm-cgi?5:mss:2861:200102:nofjdmbdkfaebemidbgl
From: Christopher R. Jones
Date: Wed, 21 Feb 2001 16:00:33 -0500
I have it working. Here is what I did:
I. MyODBC
Create a System DSN, check the following:
Don't optimize column width
Return Matching Rows
Safety
II. Foxpro
Create a Remote View, I used the Wizard. Once the view is created, you need to
modify its properties.
I am using VFP6. In the view properties screen, go to Update Criteria. Make
sure
that all fields are checked for update (the column under the little pencil is
the
update column).
Check Send SQL Updates
Check Delete then Insert.
Thanks.
It'll take a while to set up what I have already, but I'm optimistic this advice
will do the trick (Cal Evans' stuff, plus Christopher Jones')
Charles Kirby
"Cal Evans" <[EMAIL PROTECTED]> on 05/29/2001 02:36:10 PM
To: Charles Kirby/Usdcsdny@&2DC-NYS-Notes, [EMAIL PROTECTED],
[EMAIL PROTECTED]
cc:
Subject: Re: FoxPro6 and MySQL, odbc
No, you can read and write the data. The problems arise when old
"fox-jockey's" like myself try to treat the remote views exactly like dbfs.
No can do.
When creating your remote views make sure you go to the update panel and
tell it you want to actually send the sql updates. (You have to specify a
primary key for the checkbox to become available)
In short, on the project I'm working on right now we adopted the following
conventions:
1) If we have a screen that is editing a single record (like a customer
record) we create a customer object that used ADO to read and write to the
ODBC connection. (We've actually got a cool little object generator that
writes the code for us!)
2) If we need a cursor for a grid, we use SQL Passthrough. it is possible
to use ADO and another fll that can be found on the MS website to convert an
ADO recordset to a VFP cursor so you can attach a grid to it but I chose not
to do that.
3) If it's a small table (less than 200 records) then we left the existing
FP code in but removed any code that won't work with views. (indexes,
relations, locks, etc.)
I didn't mention but we are converting a 2.6 app to VFP w/ SQL. So there is
a ton of legacy code. You probably won't have to deal with that.
The bottom line is if you are careful, you can do it without a problem. But
it's not 'just like' writing FP code.
HTH,
Cal
http://www.calevans.com
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "Cal Evans" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, May 29, 2001 1:21 PM
Subject: Re: FoxPro6 and MySQL, odbc
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
