In fact, I appreciate all who have commented, and it is interesting that it looks like we will be using a combination of the suggestions made.
>Sorry, responding a bit late.
>
>Excel has a built-in limit of 64K records, so if his
>43K record is going to double, he can't use Excel.
>
>--- Stan Winchester <[EMAIL PROTECTED]> wrote:
>> 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
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
