|Sent on:||Thursday, October 11, 2012 7:47 AM|
Another thing you can try is linking the file and going through it record by record (automated, of course) and seeing where it breaks.
I’ve got a problem that maybe someone can help me with.
The application uses Access 2010 as a front end to a SQL Server 2008 back end. My app gets its information by importing data from another, purchased application that does the first chunk of work (payroll). We have to do imports because, although the other app also uses SQL Server, we are not allowed to get data directly from their database.
The payroll app exports data as tab-delimited text files [FYI, I really like this format because – unlike the CSV format -- there is no confusion as to which fields are which] which are then imported into my app with custom code and validations/error reports.
There are four files that are imported each week; three of them work just fine. The fourth one – the largest, something like 20MB – hangs / winds up throwing a debug error. The other three files are only 2-4MB. I can’t see anything wrong with the code… the size is the only difference I can see.
Has anyone run into a situation like this and have any pointers to a solution? It’s a REAL problem for my client.
Jon Seidel, CMC®
Effective Decisions... Priceless!
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Jon Seidel ([address removed]) from Berkeley Access Database Users Group.
To learn more about Jon Seidel, visit his/her member profile
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages
| [address removed]
This email message originally included an attachment.