Really disconnect a recordset?

Is there a way to completely disconnect a recordset so that it has no memory
of its server origins? So that things like
rs.Field(0).Properties("BASETABLENAME") will be blank? So it doesn't know
it was created via OLE DB for SQL Server? So that it won't validate that
"hey you really can't update that on the server"?

I've got a recordset that comes from a query where some of the fields are
derived and not actual table fields. On the client side, I want to be able
to update those fields in the local recordset without ever doing an update
back to SQL Server. Because of the underlying schema and dynamic
properties, ADO is not allowing me to "update" the these fields.

Basically, I want to take the data from this recordset and put it into
another recordset with an identical "shallow" schema -- meaning same column
names and column types but none of the other attributes that link it to the
provider, so that I can manipulate it like a local-only recordset?

Do I basically need to create a new recordset by looping through the old
one's field defs and then copy the rows one by one?

Any other solutions would be greatly appreciated.

Thanks,
Mike


.

Relevant Pages

  • Re: AcXP MS-SQL --> Sperrungen
    ... Wenn Du ein Recordset aufmachst ruft Access zunächst alle Primärschlüssel ... Und der SQL Server verwendet Fällen, wo alle Daten einer Tabelle ...
    (microsoft.public.de.access.clientserver)
  • RE: TransferText from a table with a selection-parameter
    ... > temporary table where I store the recordset inside because there may be ... Each of your users can use separate temp tables in your SQL Server database. ...
    (microsoft.public.access.modulesdaovba)
  • Re: VB-ADO-SQL Server : SQL Server performs logins after some queries
    ... The reason that I use Object types is that my code should work ... with a SQL Server 2K database (at a internet server) as well as MS Access ... recordset to a ADODB.recordset or a DAO recordset prior to creating the ...
    (microsoft.public.vb.database.ado)
  • Re: Zugreifen auf eine Stored Procedure
    ... >> wie kann ich denn auf eine Stored Procedure die auf dem SQL Server ... Die Stored Procedure soll mir eine Recordset ... > User und Passwort sind Eigenschaften der Verbindungszeichenfolge ...
    (microsoft.public.de.sqlserver)
  • Recordset is Not Updateable
    ... The query is a 4 table join. ... Server all have defined PK. ... Now with a SQL Server 2000 backend, the recordset is not ...
    (microsoft.public.access.queries)