If you know your ID's are good, you can temporarily turn on/off the ID's in SQL:
set identity_insert [databasename].dbo.tablename on on allows inserts with the ID field populated by your data, off is normal, SQL will populate the ID field on insert. Fred On Mon, Jul 16, 2012 at 1:25 PM, Stephen Russell <[email protected]>wrote: > On Mon, Jul 16, 2012 at 3:16 PM, Rafael Copquin > <[email protected]> wrote: > > You have to remember that autoincremental fields are readonly. > > What I do is something like this > > > > select myview > > scatter name oView blank fields except kw_id > > > > with oView > > .field1 = .... && you fill the object field properties with the > > values to be inserted in the corresponding field > > .field2 = .... > > etc > > endwith > > insert into myview from name oView > > > > In this manner you can insert a new record with data into the view > > bypassing the autoincremental field > -------------- > > How to do capture the ID it created for use in FKey columns for > adjoining tables? Just stuffing data into a single table is easy. > > -- > Stephen Russell > Sr. Analyst > Ring Container Technology > Oakland TN > > 901.246-0159 cell > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cajcbksqyaqmsre1u6puw8vhokxe9sxlf-nabub00oel9_s4...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
