It worked for me by set procedure command
SET PROCEDURE TO vfpconnectiontests.prg ADDITIVE
SET LIBRARY TO (LOCFILE("vfpconnection.fll","FLL"))
?httpget('http://www.google.com','google.htm',"MyProgress()", "MyTrace()")
I use .net InterOp to convert Date string to Date. This works on almost all variations of date format.
My .net method
public DateTime Date_Conv(string date)
{
DateTime d;
d = DateTime.Parse(date);
return d.ToUniversalTime();
}
Copy To filename Type csv
Creates a comma separated value file. A CSV file has the field names as the first line in the file, and the field values in the remainder of the file are separated with commas.
Yes. It's length. According to my test insert takes values upto 537 characters. My table's total length of fields is 640. So broke insert statement into insert and update. It works. But still I don't understand why it works with vfp6 and not with vfp8.
After spending little time, I found out that, enginebehaviour is not a problem. The problem lies with insert statement. It seems that foxpro gives error (command contains unrecognized phrase/keyword) on insert statement if number of fields in insert statement exceeds 12 or 13. I tested with...
I am accessing vfp8 database through coldfusion files which uses foxpro ODBC driver. I know I can specify enginebehaviour for foxpro Oledb but I don't know how to specify enginebehaviour for ODBC driver.
How do i set enginebehaviour 70 in foxpro 8 odbc? I am using coldfusion to access foxpro table. Everything was working fine in vfp6. But now I am having problem with odbc date. I ahve tried to put enginebehaviour 70 in config.fpw in home() directory. Didn't work.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.