[X]My Assistant

[LeeAnn]

I may just do that DBGuy. I have dealt with frustration over importing from Excel a long time ago, it was very similar to what this was. Got to remember also VBA is different some between Excel and Access (the := thing was a major error, it would not bomb out but it would not work like I was thinking it was lol). But it works and now I am off to a meeting regarding another project that we have been working on for a long time, something if we can implement would be cool. The process works but have not had the go ahead to implement it. Hopefully we can get things rolling after the meeting.

Thanks again everyone for your input and for getting me to think a bit outside the box.

[dmhzx]

I got so fed up with trying to import Excel to Access, that I usually end up bringing it in a cell at a time.

It takes longer than TransferSpreadsheet, but it keeps me in control, and I can then not only force fields to the type you want, but you can make corrections as you go.

I also seem to recall that once you design a transfer spec you cannot actually even see it again, never mind change it.

Good luck with getting Microsoft to do anything.

[theDBguy]

I also seem to recall that once you design a transfer spec you cannot actually even see it again, never mind change it.

This is actually possible either manually or through code.

[WildBird]

QUOTE (dmhzx)
I also seem to recall that once you design a transfer spec you cannot actually even see it again, never mind change it.

This is actually possible either manually or through code.

There is a couple of hidden tables, that you can edit (with caveats). Can be done programmatically, but I have found it a hassle personally.

I just import to a staging table, all text fields. Excel will do lots of weird stuff if it can - dates, nnumbers with leading zeroes etc, best to skip Excel if at all possible - try CSV or any other format and import as TEXT files.

Good luck