UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome Guest ( Log In | Register )

 
 Reply to this topicStart new topic
> Any pitfalls of TransferSpreadsheet?    
 
   
AvgJoe
post Nov 29 2006, 03:23 PM
Post #1

UtterAccess Ruler
Posts: 2,042
From: West Coast, USA
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,

AvgJoe
Go to the top of the page
 
+
HiTechCoach
post Nov 29 2006, 03:27 PM
Post #2

UtterAccess VIP
Posts: 18,394
From: Oklahoma City, Oklahoma
Depends... What are you doing with the data you are importing?
Go to the top of the page
 
+
AvgJoe
post Nov 29 2006, 03:33 PM
Post #3

UtterAccess Ruler
Posts: 2,042
From: West Coast, USA
Boyd,

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).

AvgJoe
Go to the top of the page
 
+
HiTechCoach
post Nov 29 2006, 03:42 PM
Post #4

UtterAccess VIP
Posts: 18,394
From: Oklahoma City, Oklahoma
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.
Go to the top of the page
 
+
AvgJoe
post Nov 29 2006, 03:49 PM
Post #5

UtterAccess Ruler
Posts: 2,042
From: West Coast, USA
Boyd,

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.


Thanx,

AvgJoe
Go to the top of the page
 
+
niesz
post Nov 29 2006, 03:55 PM
Post #6

Utter A-fishin'-ado
Posts: 17,723
From: Cincinnati, Ohio, USA . . . ><((((°>
Access "assumes" a few things when importing from a spreadsheet. I would stick to CSV to have more granular control.
Go to the top of the page
 
+
« Next Oldest · Access Forms · Next Newest »
 

Thank you for your support! Reply to this topicStart new topic

Jump To Forum:
 

Display Mode: Standard · Switch to: Linear+ · Switch to: Outline

Track this topic · Email this topic · Print this topic · Subscribe to this forum

RSS Go to Top  ·  Lo-Fi Version Time is now: 18th May 2013 - 09:56 AM