Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Tableupdate() on local view fails after editing memo fie
Message
 
To
26/01/2000 20:11:04
Scott Knight
Human Resources Development Canada
St. John's, Newfoundland, Canada
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00323294
Message ID:
00323349
Views:
28
Scott,

What happens when you do a AERROR(laError) after the table update fails. The laError array should get populated with some more useful information.

Cheers,

Andrew

>I am having some problems when trying a tableupdate() a local view after editing a memo field. Some background...The local view selects all the fields,has all fields marked as updateable, send updates is checked, the required keys are set O.k. I have optimestic table buffering set on the view and no buffering set on the table. I can edit any other field except a memo field and the tableupdate works o.k and the data is written to the table as planned. If I edit the memo field and Tableupdate() it fails. The strange thing is on an add it works perfect. I had a glitch earlier where one of the field names was "group", I assume because it is keyword in SQL a syntax error was created. The field name in this case is empdesc. I also tested this from the command prompt using the view, setting the cursorprop, modifying the data through a browse and I got the same results. As long as I did not edit a memo field everthing was O.K. and the tableupdate would work ???
>
>Any insight would be greatly appreciated...
>
>Thanks
>
>
>Scott K


If we were to introduce Visual FoxBase+, would we be able to work from the dotNet Prompt?


From Top 22 Developer Responses to defects in Software
2. "It’s not a bug, it’s a feature."
1. "I thought I fixed that."


All my FoxTalk and other articles are available on my web site.


Unless specifically identified otherwise, anthing posted here is purely my opinion and may or may not reflect the policies or practices of Microsoft.
Previous
Reply
Map
View

Click here to load this message in the networking platform