Search results

After much dinking around, I was able to get Access to link to the text file using my IMEX spec in one statement, and then use the linked table in your INSERT query to proceed. WooHoo! I am very pleased - thanks again for sharing your knowledge.

Thank you once again for all your time and help. Unfortunately I'm enough of a newbie that I have no clue how to upload an empty database with the necessary objects to this site, otherwise I would do so. I'm starting to wonder if I have a too-old version of Access (MS Office Professional 2010...

The spec absolutely exists, because I have already imported/exported with it many times successfully. However, Access only returns the 3625 error code when attempting to use it to link to the text file. I will do some Googling on my end to see if I can better understand how to open a text file...

Got it. I have already created the IMEX spec, so that's not the issue. Here's what sSQL looks like using my data: INSERT INTO AL_TR_AL_Link (ALBUM_ID, TRACK_ID, ARTIST_ID, LOCN_ID) SELECT T.ALBUM_ID, T.TRACK_ID, T.ARTIST_ID, T.LOCN_ID FROM...

Thanks Pat. The only portion of the solution that @ebs17 posted that I'm still unsure of is how to create the DSN NameSpec. Would I have to create a different DSN for each and every different table that I'm importing?

Wow, thanks for your quick response! All the above looks really cool, but there are some moving parts that I don't know how to fit into the puzzle. When I generate the sSQL string, it looks like this (for my test sample table): INSERT INTO AL_TR_AL_Link (ALBUM_ID, TRACK_ID, ARTIST_ID, LOCN_ID)...

- All - I have reviewed many threads across this site and elsewhere, but didn't see an answer that fit my exact situation. I have a form with a multi-select listbox that I use to allow me to easily import and export table content from my database using an import/export specification. Here is a...

Hello to one and all. I have joined this forum in the hopes that some of my obscure, pesky Access problems might be answered by those far more knowledgeable than I. I've worked with Access since 1992, but in no way, shape, or form could I be considered an expert - I know just enough to be...