Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I'm pulling a recordset of data based on a query into Excel; currently
I flip through the Field.Name and Field.Type properties to populate the header rows with recordset names and types (enumerating the types as adInteger, adVarWChar, adBoolean, etc). I don't find a way to test the recordset to see if the field came from a table's primary key... which doesn't seem too taxing. Looks like I would need to go to ADODB.Connection.OpenSchema and test the originating table to find its keys. Could that be right? Feels like I am missing something obvious, but I hope you'll humor the question anyway! Thanks, Jeff |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Cannot use recordset twice with copy From recordset | Excel Programming | |||
ADO Recordset | Excel Programming | |||
ADO recordset | Excel Programming | |||
Need ADO Recordset Help | Excel Programming | |||
Type recordset/recordset? | Excel Programming |