Nov 29 2006, 03:23 PM
Greetings and Happy Holidays. Here's the deal - I've got a db that has an import routine for a csv file. The file is created via Business Objects (formerly Crystal Reports). Is it "cleaner"/"easier" (dare I say "smarter?") to save the output as an Excel file and use the TransferSpreadsheet command instead of my current import routine?
Thanking you in advance,
Nov 29 2006, 03:27 PM
Depends... What are you doing with the data you are importing?
Nov 29 2006, 03:33 PM
The current csv file is parsed out into a dozen fields (if I remember correctly). Once parsed, a table is created (via a Make Table query). This table "drives" the main form. (I hope I answered your question. Thanx for your quick reply).
Nov 29 2006, 03:42 PM
It may save a step if you use the transfersheet method. You would have to do some testing to see if it really works better.
Normally you do not need to manually parse a CSV file. Not sure what you are "parsing".
I have found that it is normally better (smarter) to go with a generic file format like CSV. Using a spreadsheet format could run into compatibility issues with drivers when software is upgraded which could be the one creating the file or the one reading the file.
Nov 29 2006, 03:49 PM
Good point (compatibility issue(s)). I need to find out from the user exactly what kind of problem she's having.
I guess for now, I'll stay with the csv file.
Nov 29 2006, 03:55 PM
Access "assumes" a few things when importing from a spreadsheet. I would stick to CSV to have more granular control.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here