William Vaughn
2/13/2008 6:01:00 PM
Oh, sorry, I thought you were using a ... (opinion deleted)
In this case, I still suggest using SSIS or at least SqlBulkCopy to upload
the archive data to a SQL Server and strip off the old rows with a
Delete...oh... right, the customer does not have a ...
This is like trying to play badminton in the hall closet.
I'm sure one of the JET heads will kick in and help.
--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
____________________________________________________________________________________________
"Steve Kelley" <skelley@proteaninstrument.com> wrote in message
news:LSmsj.31435$1f.4421@bignews9.bellsouth.net...
> William Vaughn wrote:
>> This should be done on the server, not on the client. Write a stored
>> procedure to do the work and send the data to another database on the
>> same server or on a linked server. I would probably accept a SELECT * to
>> pick up all columns... as in
>>
>> SELECT * INTO OtherDB.dbo.MyArchiveTable WHERE <some condition>
>>
>>
> Thanks for the response. My situation is a bit different from most. We
> produce an instrument and as the user uses the instrument the results are
> stored in an Access database. There is no server per se, the instrument
> control application is the only access the user has to the data unless
> he/she has MS Access installed (most likely not). As the database grows
> the users may want to archive some of the data and remove the archived
> data from the parent database. I present the user with a dialog box that
> allows him/her to select batches and a date range to
> archive, build the constraints string then archive the data. Database
> programing is not my forte and I have never created a stored procedure.
> Given the additional info do you still recommend that approach?
>
> --
> Steve Kelley