Microsoft
Software
Hardware
Network
Question : Import a TXT file with >255 fields into Access 2003
Hello all,
I am having an issue with a file I'm receiving from another external provider.
In a nutshell, I am getting a delimited text file with 288 fields and due to company policy I am being forced to work a solution to pull these files into Access 2003. Obviously the source db is not normalized and they are not willing to change their output file (I must also bring in historic files using this format).
I looked through another post where a person in a similar situation suggested using an import spec to break the file into two or more tables (which would allow me to normalize on my end)...the problem I'm having is that even calling the import specs in VBA I'm getting an error "too many fields" from access.
I've loaded one of the specs I'm trying to use where I identified each field and then skipped about half of them.
Am I doing this spec right?
Answer : Import a TXT file with >255 fields into Access 2003
Ok, you guys have the right idea, and simply have some issues with the code itself. Let me know if you run into any issues with the code above. BTW, IsValid is a function I use to see that the file exists in the location specified.
Leon
Random Solutions
Windows Home Server Activation
Type Mismatch with AddAlltoList
Grid: display one record in different rows
How do I deal with system event ID 7011 (Timeout waiting for a transaction response ...)
Delete files in folder and delete subfolder
Is it possible (and practical) to move/import an existing blog into SharePoint?
Temporary Table in SQL Server 2008
UNION all view % is not updatable because a partitioning column was not found
Update Pivot Table Based On Cell Reference - Error Handling
Alternative to sysprep on windows 7 home premium