![]() |
Export to Access, Workbook Treated as a Query Response
I ran a query on the mainframe and via ODBC, pulled the results into Excel.
I had a need to add a column of data. I did so and I saved the Excel file. When I go to Access (after importing the Excel spredsheet as a new Access table), my change (the additional column) is not there. I got to poking around and for some reason Access is treating the worksheet like it's not a worksheet at all, but instead, like it's a query (or a response to a query). Is there anything I can do in Excel to prevent or reverse this? Here's how Access "views" the range - "UKRM!Query_from_AS400 |
Export to Access, Workbook Treated as a Query Response
hi
not sure but when you imported the query from AS400, did you rename the range in excel. the query imported into excel and excel gave it the name query_from_AS400 and that is the named range that access imported. if you did not resize the named range (as well as rename) then access did not pull in any extra columns. it pulled the named range that was imported into excel. my thoughts(guess) regards FSt1 "ConfusedNHouston" wrote: I ran a query on the mainframe and via ODBC, pulled the results into Excel. I had a need to add a column of data. I did so and I saved the Excel file. When I go to Access (after importing the Excel spredsheet as a new Access table), my change (the additional column) is not there. I got to poking around and for some reason Access is treating the worksheet like it's not a worksheet at all, but instead, like it's a query (or a response to a query). Is there anything I can do in Excel to prevent or reverse this? Here's how Access "views" the range - "UKRM!Query_from_AS400 |
All times are GMT +1. The time now is 12:53 AM. |
Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
ExcelBanter.com