R
robert d via AccessMonster.com
I currently use the TransferSpreadsheet function for creating the table
needed to hold the imported Excel spreadsheet data. Since the holding table
doesn't exist the function will create it. This frees me from having to know
how many fields to create, etc.
However, now I want this holding table to be created in a temporary database
so that I can free my front end from the bloat that's caused by the import of
the data.
Is there a way I can create this table in the temporary database while still
not having to specify the structure of the table. This table is only a
holding table and will be killed after the import, so I can't see spending
the time to create a lot of code for specifying its structure, if I don't
have to.
So the current code is:
DoCmd.TransferSpreadsheet acImport, , mTable, mFile
Is there someway to include the path with the table name (currently in mTable)
.. Currently mTable is only the table name.
Thanks.
needed to hold the imported Excel spreadsheet data. Since the holding table
doesn't exist the function will create it. This frees me from having to know
how many fields to create, etc.
However, now I want this holding table to be created in a temporary database
so that I can free my front end from the bloat that's caused by the import of
the data.
Is there a way I can create this table in the temporary database while still
not having to specify the structure of the table. This table is only a
holding table and will be killed after the import, so I can't see spending
the time to create a lot of code for specifying its structure, if I don't
have to.
So the current code is:
DoCmd.TransferSpreadsheet acImport, , mTable, mFile
Is there someway to include the path with the table name (currently in mTable)
.. Currently mTable is only the table name.
Thanks.