Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Why the difference?
Message
 
 
To
28/06/2001 15:56:41
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00523778
Message ID:
00524904
Views:
11
I guess you can only do it for SPT cursors which, BTW, is where I have only done this because almost all my work is in Oracle. IMO, this is a really stupid restriction. I guess you could create a DSN-less connection to that table using SQLStringConnect(). This is sooo convoluted. IF you decide to go this way, get my ODBC_DSN class from UT Downloads.

>>What does adding the NOFILTER clause at the end of the SQL do for you?
>
>Just tried it, and there is no difference at all. I'm getting the error message "Property is invalid for table cursors", on each and every cursorsetprop statement. According to the help file:
>
>
><b>Property is invalid for table cursors (Error 1468)</b>
>The property is not supported for cursors based on tables; it applies only to cursors based on views.
>
>Use the property only for view cursors.
>
>
>The whole point of this exercise, though, was to not use a view.
>
>But, is this how you are doing it, and it works for you?
>
>Alan
>
>>
>>>Mark, I hate to be a pest, but I've been playing with this, and I can't figure out how to make it work.
>>>
>>>After creating the cursor using SQL, when I try to issue the CursorSetProp's, I get a bunch of errors saying that they are invalid on table cursors.
>>>
>>>Clearly I'm missing something basic here. How should I be issuing the SQL statement? I'm using a normal "Select * from ctracts into cursor v_contracts", and I can't use any of the cursorsetprop()'s against v_contracts.
>>>
>>>I know about making cursors updatable using "Use DBF() again in 0", but I don't see how that really helps in this situation.
>>>
>>>Any help would be appreciated.
>>>
>>>Alan
>>>
>>>>The problem you will have at runtime is clashing view creations from multiple users doing this within the common DBC. I still recommend creating a cursor using SQL. You can then make the cursor updatable:
>>>>
>>>>CursorSetProp("SendUpdates",.t.)
>>>>CursorSetProp("Tables","dbcname!mytable")
>>>>CursorSetProp("KeyFieldList","keyid")
>>>>CursorSetProp("WhereType",1)
>>>>CursorSetProp("UpdatableFieldList","keyid, descript")
>>>>CursorSetProp("UpdateNameList","keyid mytable.keyid, descript mytable.descript")
>>>>CursorSetProp("Buffering", 5) && optional [my preference]
Mark McCasland
Midlothian, TX USA
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform