Depending on how big the database is, if it is not too big why not just loop
over each record in the new database and update the old records. Checking in
each loop to see of the record is new, if so, Insert it.
This is assuming that they do not change the database structure on you. This
whole process would be made faster if the database that they feed you was
designed to put a timestamp on each record any time a record was added or
updated. That way you could just query the database for anything that has a
timestamp after your last update.
You could make it super easy on yourself by providing the person who gives
it to you a url to go to and upload the new database to. The web site would
automatically update the database, and the updater would know when the new
data is up right away.
jon
----- Original Message -----
From: "Peter Benoit" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Friday, December 22, 2000 1:38 PM
Subject: RE: [database update?]
> It's a whole new access DB
>
> -----Original Message-----
> From: Alex [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 21, 2000 3:08 PM
> To: CF-Talk
> Subject: Re: [database update?]
>
>
> do you update the database (SQL statement) or replace the database with
new
> access DB?
>
> Peter Benoit <[EMAIL PROTECTED]> wrote:
> I have an ODBC connection to my access database. Once a week I update
that
> connection with a new database. It seems to take roughly 15 mins or so
for
> that update to take place. Is there a reason for that, and can I shorten
> the length?
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
