Hi Ricardo,
>Let's go to the question. I have once the problem you had: at INSERT works, and at UPDATE don't. It's simple. You cannot use the references of textboxes (or other objects) at the UPDATE. Use variables to support it.
>But, after reading your message, i get scared with another thing: are you updating all the fieds of your table like that? Why don't you use ControlSource of your objects, and do a Tablupdate? I'm sorry if i'm against your philosophy, or if i'm saying anything wrong, because i'm not seeing the problem.
This question was for a *very* quick fix of someone else's application (which was a port of some old Fox2x code that used multiple REPLACE's, one for each field -shudder-). For reasons which remain their own, the developer wasn't (and isn't) interested in binding the controls (I still don't know why).
I ended up solving the problem by using a single REPLACE command. I guess I was just VERY surprised that INSERT-SQL would accept an object reference and UPDATE-SQL would not. Seems to be a bit of an *OVERSIGHT* to me... (g,d,&r)
My normal methodology is to bind the control's ControlSource or RecordSource to the necessary data item in the view -- so we agree on the philosophy part (g).
Thanks,
Evan Pauley, MCP
Positronic Technology Systems LLC
Knoxville, TN
If a vegetarian eats vegetables, what does a humanitarian eat?