Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP8 OleDB Still no Schema?
Message
General information
Forum:
ASP.NET
Category:
ADO.NET
Miscellaneous
Thread ID:
00739094
Message ID:
00740621
Views:
27
Nope,

Same Error;

Additional information: Dynamic SQL generation for the UpdateCommand is not supported against a SelectCommand that does not return any key column information.


I do notice that after:

m_DataAdapter.FillSchema(m_DataSet,SchemaType.Source,"customer");
m_DataAdapter.InsertCommand = m_CommandBuilder.GetInsertCommand();
m_DataAdapter.UpdateCommand = m_CommandBuilder.GetUpdateCommand();


The .InsertCommand is set to "Insert Into customer ..... ?,?,?"
But the GetUpdateCommand still bombs out with the above error.

I think were getting closer, The FillSchema did get the Column infomation, but We are still missing the Primary Key info. Inside the CDX (Compound Index) their are multiple collating sequences called TAGS. Normally under foxpro you do a "SET ORDER TO ????" to set specify. The customer.dbf has TAGS for CUSTNO,LASTNAME and STATE. I should have to specify which one i've made unique. In this file case it's the CUSTNO Tag. I see that the DataTable has a .PrimaryKey property, but it seems to be limited to just the table for performance, not the schema for updating.


Their has to be a way for a DBF to work, but this one is puzzlng.

Thanks again for your continuing help,
Mike
Previous
Reply
Map
View

Click here to load this message in the networking platform