Garett,

it was a good suggestion. I built a debug version of the executable that logged errors from the connection object. Funny enough it reported 1 error with the same description, error number and source as OLEDB provider.

I started thinking how I can narrow it down. This VB executable is on the workstation and the table it is trying insert into is on the server. When I open the table in vrunfox I can append record , edit records etc. So the tables are not corrupt and I can access them from the workstation no problem.

I decided to simulate a standalone scenario and moved everything to the workstation. Bingo! It worked fine.

One more detail it is a Novel Server. We do have clients who run it on Novel network and have no problems.

It looks like it is a problem for VB app to access the VFP table due to some kind of Novel Server setup.

At any rate I still need help finding the solution!