You can still use the DTS.
Look up "Data Driven Query Task" in the Online Books. It can analyze the
source data and decide which out of four (insert, update, delete and user)
queries to run on the current row. Might be what you're looking for :)
> > Hello Chris !
> > Try to use the DTS to get the data in the original database. In the
> > just insert non-existing data, or use a query to insert only
> > data.
> > Hope thatll help you, dont hesitate either to ask us ;-))
> > Jens S?meyer.
> Thanks for the help. This solution only addresses part of the problem. I
> also need to be able to import changed data. Any ideas? I'm beginning to
> think that it might be easier (since it's only about a days worth of data)
> to have our data entry people re-enter the data in the old system so that
> when we convert (for the second time) we won't have to deal with the
> headaches involved.
> > > Howdy all.
> > > Here's my situation. My department recently upgraded a database from
> > > Data-flex to SQL. Through usage the following day, we found many
> > > data/linking errors and we went back to using the data-flex version of
> > > database until we could resolve the problems. We finally tracked down
> > > problems and have corrected the information, and here is where the
> > > part comes in. The SQL version of the database has somewhere around
> > > user defined tables. During the day we were using the SQL version, we
> > > entered many new records. What we would like to be able to do is
> > the
> > > original data (and everything that we have added since returning to
> > old
> > > system) into a new SQL database. Then, we would like to compare the
> > > with the original installation of the SQL version and update the
> > > necessary. Is there a way to do this in a quick, efficient manner or
> > would
> > > it have to be done on a table by table basis?
> > > If you need any more information, please don't hesitate to ask. I
> > > provide as much info as possible.