AppendChunk

[csmajor231]

I need a favor guys, I took over this site that uses Visual FoxPro as a database, not the greatest choice but everything works except for one thing. The person uses Memo field to hold client complaints. They are using AppendChunk to do the insert because of the 254 char limitation. For some reason where it is going to open the table I get a exception error "open" this happens when they are using a table that is live with client orders. if they use a table that is not in use then it works find. any help would be appreciated.

[BigDaddy]

Could you be more specific? Is this when you try to do an insert from an ASP page? What's the error received? What's the specific wording?

[whammy]

At least we know he isn't using Access 2000 (or SQL Server) and ASP, since he already noted that he's using a different database, and we have many more characters readily available... :D

I'm not familiar with the "memo" field of your database program... can you list your software capabilities? ... although this kind of situation sounds like it "could" be a network thing... (at least BigDaddy might think so too referencing our working environment... lol) :D

It also sounds like there might be some security restrictions on the live table that are causing this. Which may be good! Or perhaps you can change the field type in your database to accept more characters? I know Access 2000 accepts more than that (8000 to be safe, I think in a memo field).

I really wish I could help you, but to me this sounds like an issue with Visual FoxPro that you might need to solve by contacting their "support", after talking to your Network Admin. I'm not familiar at all with the software... is anyone else here?

[Alekz]

Hi,
I'm not sure for all this, but chances are I remember well...
Fox Pro uses .dbf files which means normal DBASE tables. Dbase tables store BLOB fields such as MEMO in separate files - *.dbt and if I remember well in some circumstances requires exclusive access to the tables...
The other problem You may have - Fox Pro uses a native driver to access DBF's and it is not the same as the driver used in ADO or ODBC.
You can try the following:
Create a DSN especially for the table that causes problems and make You fox-pro app use explicitely this DSN. Make ASP use the same DSN - this should eliminate driver concurrency issues...

Alex