ADO update and tables with more than 127 fileds
- From: "Roberto" <non.scrivere.a.celiro@xxxxxxxxxx>
- Date: Tue, 1 May 2007 00:27:46 +0200
I have a system with many tables and several with about 280 fields (please
don't ask to modify the structure, I inherited a quite large and complex
project), this is on client side, basically the code performs an initial
query to load recordsets (from tables), bounds the recordsets to table
views, allows the user to edit values, then writes modified values to
recordsets and finally calls update() to write data on tables.
I noticed that for the big (280 fields) tables the code instead to modify
directly the
edited record (by setting new values and then calling update) deletes the
record, adds a new record, writes data on the new record and finally calls
update(), a note explains
that this was done to circumvent the 255 field limit of the ADO update
query (ACC2000: "Too Many Fields Defined" Error Message in Update Query).
I would hope there is a more efficient way to solve this problem, perhaps
there are methods/variables to control (by program) the complexity of the
query originated when calling update() and reduce the complexity (for
example by processing only a limited number of fields in each query), any
suggestions ? (I am very reluctant to replace all the calls to update() with
my own code, the recordset object is really easy to use)
Thank you,
Roberto
.
- Next by Date: Deploying Windows Application with ODP .NET
- Next by thread: Deploying Windows Application with ODP .NET
- Index(es):
Relevant Pages
|
|
