If the mechanism is simple for all concerned, I wouldn't even think twice
about doing it that way, unless the load on the server is already pretty
high.
cheers,
barneyb
-----Original Message-----
From: Stan Winchester [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2003 1:46 PM
To: CF-Talk
Subject: Import/Export - Excel to/from Access/SQL Server
I have a client who is running an ecommerce site with an Access database
backend, which will hopefully be upgraded, to SQL Server 2000 very soon.
The issue is he has 7,800 records in one table and 43,000 records in
another
table; both tables will be doubling in size very shortly. My client wants
to
do all of his data entry in Excel, and then do an import into his tables
to
add new records, and edit/delete existing records. I had thought about
doing
an import/export routine to/from an Excel file, but the export alone pegs
the server at 100% CPU for almost 25-30 seconds. I am interested in
setting
up the most efficient method that will minimize the load on the server.
Any suggestions would be appreciated!
Thank you,
Stan Winchester
Aftershock Web Design, LLC
[EMAIL PROTECTED]
http://www.aftershockweb.com/
Phone 503-244-3440
Fax 503-244-3454
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
