Keep Files In Sync and Avoid Collision I/O Errors
Runtime Replicator tracks which objects in a library have changed, logs the changes, and then copies the new objects to the destination library (replication). The replicated ‘runtime’ directory prevents collision I/O errors if you try to run an application while checking objects in and out during development.

Collision I/O errors can occur when a teammate is running the application from the same library-list you are saving to. This can cause problems when checking in an object through version control, as you may lose the check-out status when the I/O error occurs.

Use Runtime Replicator to check objects in and out from the normal directory structure and then run the application from a duplicate ‘runtime’ directory. Runtime Replicator creates the runtime directory on your local drive, checks it periodically for any changes in the original libraries, and copies the objects to the runtime directory without the developer lifting a finger!

• Network traffic is minimized.
• Developers never have to exit the application.
• Automatic object replication.
• Always run with the latest objects.
• Faster execution speed.
• Check-in and regenerate objects without PB I/O errors.
• No batch file to run.
• No file I/O errors.