not Excel (primary goal was custom reporting, not just
export/edit/re-import).
I used XML to transfer data from the web server to the client application.
I wrote server and client modules that each handled the appropriate
serialization and de-serialization. It's a lot of work, but it worked out
well and client was very happy in end.
HTH,
Sam
----------------------------------------------
Blog: http://www.rewindlife.com
Chart: http://www.blinex.com/products/charting
----------------------------------------------
-----Original Message-----
From: Stan Winchester [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2003 4: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
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
