Versions des environnements
Network:
Windows Server 2012 R2
Virtual environment:
VirtualBox
I hated the stuff you had to set in updatable views, also the redundant way to set them (had some helper funcs to make it more DRY around Y2K), but nowadays I try to always work with CA. Point a builder to remote source, tweak a bit, cursorfill() where .f., append and tableupdate().
A lot of the unDRY thngs can be set at a CA parent class...
>I'm using ODBC-based remote views to insert data into SQL Server tables. The general process is:
>
>1. CREATE SQL VIEW MyView ...
>2. USE MyView
>3. APPEND FROM SomePath\SomeVFPTable.DBF
>4. =TABLEUPDATE( .T., .T., "MyView" )
>
>The column names, types and sizes are the same in the VFP table and the destination SQL Server table (names yes, types as close as they can be).
>
>All of the above runs without generating any errors. However, there are no rows in SQL Server after the code runs (should be 92 rows for the test table I'm using).
>
>I have SET MULTILOCKS ON but I've made no other changes to default remote view settings. I suspect I need to set some remote view properties for MyView via CURSORSETPROP() before APPENDing the data and running TABLEUPDATE(). Can someone remind me which properties I need to set?
>
>UPDATE: it looks like, at a bare minimum, SendUpdates needs to be set .T. Any other recommendations for best performance/efficiency? I'm thinking setting the view to Optimistic Table Buffering given the type of updating I'm doing.
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement