FoxWeb uses the native VFP engine, so you should never need to use ODBC to access DBF files. Just use regular VFP commands.
| FoxWeb Support Team support@foxweb.com email |
Sent by dabby tai on 03/05/2008 08:26:20 PM:
Dear,
If i can't use ODBC, what method i can use?
Please HELP, TKS!
If i can't use ODBC, what method i can use?
Please HELP, TKS!
dabby
Sent by FoxWeb Support on 01/07/2002 09:27:33 PM:
VFP's memo fields can contain large amounts of data, but the problem here is your use of ODBC. A lot of ODBC drivers limit the size of text or memo fields to 254 characters. Obviously, if you are writing to a FoxPro table from a FoxWeb script you do not have to use ODBC.FoxWeb Support Team
support@foxweb.com
Sent by Brian Moran on 01/07/2002 11:06:31 AM:
With the regards to FoxPro memo field...is there any reason why I should not be allowed to insert more than 225 characters with an Insert statement.
I can insert as many characters when I type directly into the field using the db interface, but when I use an insert statement, it errors out at 225.
ERROR:
Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
[Microsoft][ODBC Visual FoxPro Driver]Command contains unrecognized phrase/keyword.
I figured it had to be a driver problem but I just spent a few hours making sure everything is up to date. They are still using 6.0 so I dont know if this is something that was fixed in 7.0.
With the regards to FoxPro memo field...is there any reason why I should not be allowed to insert more than 225 characters with an Insert statement.
I can insert as many characters when I type directly into the field using the db interface, but when I use an insert statement, it errors out at 225.
ERROR:
Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
[Microsoft][ODBC Visual FoxPro Driver]Command contains unrecognized phrase/keyword.
I figured it had to be a driver problem but I just spent a few hours making sure everything is up to date. They are still using 6.0 so I dont know if this is something that was fixed in 7.0.