ODBC *is* slow.....and, yes, use INSERT INTO and UPDATE....you need to use the INSERT INTO for any table with a primary key defined in Access or you will get a very nasty message via ODBC about primary key violation.


>OK, everything is working. Man! ODBC is slow.
>I'm appending 16,000 records to test speed using:
>by
>APPEND BLANK
>REPLACE ....
>REPLACE ....
>etc...
>
>Should I be using UPDATE and INSERT INTO instead?
>
>
>>Kevin
>>
>>TGIF....I meant 1 not 0. Sorry. Try it all again with 1 (no buffering)
>>
>>
>>>When I have the view open in the current work aread and I do this:
>>>lSuccess=CURSORSETPROP("Buffering", 0) I get "Property out of bounds."
>>>
>>>If I make a change in the browse window and then do TABLEUPDATE(2,.T.) the change appears in the browse. But if I close it and browse again the change is gone. ??
>>>
>>>
>>>>Make sure that there is no buffering with=CURSORSETPROP("Buffering",0) -or-
>>>>make sure you issue a TABLEUPDATE(2,.T.) before closing the table.
>>>>
>>>>>
>>>>>OPEN DATA dbc
>>>>>CREATE SQL VIEW TWCView;
>>>>> CONNECTION TWCustomers SHARE;
>>>>> AS SELECT * FROM access.customer
>>>>>
>>>>>I make changes but they are only saved to the local temp table, not to the actual connected Access database? I thought you could write to the file to?
>>>>>
>>>>>>Kevin ---
>>>>>>
>>>>>>Well...Not many, really, if you're just appending records.
>>>>>>
>>>>>>
>>>>>>>Ok, great, just got an ODBC view into an Access database. I have heard that performance with ODBC is pretty bad. If I am just appending records to an ODBC database once a night, I take it performance isn't really an issue. What database functions are hindered with ODBC.
>>>>>>>
>>>>>>>>It can read/write them as remote views via ODBC. There is no native use of Access databases.
>>>>>>>>
>>>>>>>>>Does VFP 6.0 import and export to Access databases? Or even better, will it write and read directly to an Access database?