ZapTools Updated

[fla]

Here's a version that gets rid of the config file for ZapInterface users that don't need gbpvr database support like XRecord. The changes are minimal and cleaner than the config file copying hack I tried first.

Changes:

DatabaseHelper.cs
o Hardcode the zapdb to db3
o gbpvr database support enabled with bool argument to initialize()

zapimport:Main.cs
o Add bool argument to initialize() to enable gbpvr database support

ZapImport.exe.config
Deleted the lines regarding zapdb

I've tested this with zapimport (with config file) and XRecord (no config file ). Any chance something like this could make it into an official release of ZapTools? It would allow XRecord to sync up and avoid conflicts with EWA users.

2007-03-01: Removed the attachement since the latest ZapTools release has the changes

[UncleJohnsBand]

Here's a version that gets rid of the config file for ZapInterface users that don't need gbpvr database support like XRecord. The changes are minimal and cleaner than the config file copying hack I tried first.

Changes:

DatabaseHelper.cs
o Hardcode the zapdb to db3
o gbpvr database support enabled with bool argument to initialize()

zapimport:Main.cs
o Add bool argument to initialize() to enable gbpvr database support

ZapImport.exe.config
Deleted the lines regarding zapdb

I've tested this with zapimport (with config file) and XRecord (no config file ). Any chance something like this could make it into an official release of ZapTools? It would allow XRecord to sync up and avoid conflicts with EWA users.

Excellent! Thanks....looks clean....I'll post an update release shortly.....

[ww4397]

Put this in front of the zapimport command "start /wait /low"

zapimport

becomes

start /wait /low zapimport

Thanks fla this works nicely.

Thank you, too, David for the initial tip.