Missing History entries on Remote Office

[AWollner]

Hi all,

in a remote office database are 20.000 fewer entries in the history table, as in the main office.

If possible, we don't want to cut a new remote office db.

Is there anything to be said against updating/inserting the missing entries via sql query? The missing entries seems to be old entries, the actual ones are syncing fine.

Thanks

[MikeSpragg]

You cannot update them - it will send an update - which, as they don't exist - will just lead the SQL server on remote to spin its wheels for a while. You'd to drop and re-create them - I'd drop them into a table. Then, drop them via Admin / SQL and then re-import them (which you can do via importwiz. That way, they'll be re-created. Or you could script it - two recordsets - update them to X....ID and then drop and then create them as H...ID and then drop the X..ID - as you want the ID's to remain the same.