To answer your second question the Sybase database is not accessible on that part of the network, that would have made things too easy :)
This is actually a recurring task, how would you suggest to do it better?
----- Original Message -----
From: Barney Boisvert
To: CF-Talk
Sent: Monday, December 15, 2003 3:16 PM
Subject: RE: Problems with Nulls
I suppose youre kiling your access db. You could batch them so you only do
a few hundred at a time, and then just rerequest the page to do the next
500. Keep your place in the sybase recordset with a session variable or
something. If this is a recurring thing, then you might have to get more
creative, but from your original post, it sounded like a one-time deal.
Perhaps a better question to ask would be if you've already got a Sybase
server set up, why are you using access for this new app?
Cheers,
barneyb
> -----Original Message-----
> From: Mickael [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 15, 2003 12:06 PM
> To: CF-Talk
> Subject: Re: Problems with Nulls
>
> Hi Barney,
>
> Thanks for the tip. I keep getting this error
>
> Request canceled or ignored by serverServer busy or unable to
> fulfill request. The server is unable to fulfill your request
> due to extremely high traffic or an unexpected internal
> error. Please attempt your request again (if you are
> repeatedly unsuccessful you should notify the site
> administrator). (Location Code: 26)
>
> I am trying to insert about 36000 account that may have up to
> 3 records per account, it seem that I am overloading my
> server? There is nothing else running. Is there a way to
> throttle it back?
>
> Mike
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
