Thank you very much for your advice, I guess I'm wasting my time in
this 'problem'. I'm going to check that class, it seems pretty useful.
And by the way...yes, this is a born-dead app (at least on the client
side) and it's likely to be ported to .NET in the future, but like I
said before, it's
Fernando Moreno wrote:
Hi all, I'm using visual foxpro 9 -not my decision- for a client
application. Statements are writen as the typical sql string and sent
through ODBC.
i like foxpro it has its quirks as do all languages. Only concern if
this is a new app Foxpro has been killed by
Completely forgot take a look at Cursor Adapter Class, also any cursor
in foxpro can be made be updateable with CURSORSETPROP( ) function
removing the problem of writing Update's and Inserts
Fernando Moreno wrote:
Hi all, I'm using visual foxpro 9 -not my decision- for a client
Hi all, I'm using visual foxpro 9 -not my decision- for a client
application. Statements are writen as the typical sql string and sent
through ODBC.
For numbers, I have to convert them first to string and then remove
the spaces, the code looks like this: sql_string = some sql +
alltrim( str(
Fernando Moreno azaze...@gmail.com writes:
For numbers, I have to convert them first to string and then remove
the spaces, the code looks like this: sql_string = some sql +
alltrim( str( some_number ) ) + more sql; I can combine alltrim and
str in a third function but it's still tricky. A
