an idea could be to use a simple batch like the following (when AB is not running):
xcopy c:\programmi\amibroker c:\programmi\AB2 /E /I /H /Y /Q C:\Programmi\AB2\Broker.exe to start the second istance in a different location having a fresh copy of AB with all last .afl, configuration, layouts etc, to be used well knowing that no changes will be saved in the "main" location ever time the batch is run everything in AB2 will be overwritten by a new copy of AB it could help to have a second istance ready to be launched to do an optimization while you can continue to work in the first istance. Of course also the results of optimization will be lost at any batch run... but you can manage this :-) --- In [email protected], "Tomasz Janeczko" <gro...@...> wrote: > > Hello, > > You can run two instances but please keep in mind that > a) if you are running off the same database the last write to database counts > (overwrites previous writes) > > b) it is advised NOT to add new charts to existing layouts when running two > instances from very same database and same location because > newly inserted charts won't be accessible in another instance. > > Best regards, > Tomasz Janeczko > amibroker.com
