File - Database Comparison Utility dbComp

[TonyE]

File Name: Database Comparison Utility dbComp

File Submitter: TonyE

File Submitted: 9 Mar 2007

File Updated: 17 Nov 2011

File Category: Tools/Docs

Authors: Jon Reimer, Darren Buckley, Tony Eischens, Russell Sharp

 

MS Access based tool to compare two H3ANW databases. Older versions (i.e. 2006.02) should be used for H2 and pre-3.8.0.0 databases).

 

Current version (2011.02) has only been tested on H3ANW 3.10.1 with H3RE_3_10.mdb

 

Maintained by Tony Eischens

 

Click here to download this file

[TonyE]

Updated version 2007.04, it will only work with ANW 3.8 databases. Use 2006.02 for previous database formats.

 

http://harpgamer.com/harpforum/index.php?a...amp;showfile=18

[TonyE]

Updated version 2007.06, now in Access 2000 format. Created against H3RE_2_27.

 

http://harpgamer.com/harpforum/index.php?a...amp;showfile=18

 

o 2006.06 2007/09/16

 Converted format of dbComp to Access 2000, this was required to update the t1* table structures since the H3RE is in Access 2000 format.

 Matched up flags to H3RE_2_27

 Added Phased Array Radar flag to sensor ECM types

 This version of dbComp does not handle the full capability of H3RE_2_27

• lCSCodes is not compared at all, seems to be the biggest lack of functionality at present, though there are other lesser limitations.

o 2007.05 unreleased

 Changed RepairCapacity to FuelTransferRate

 Continued structure matching

[JanMasterson]

here are some requests in SQL format that, thanks to Tony's help, i created to ease my work.

 

 

QueryList_BOLWeapons

 

it list all the weapons that can be fied with the CTRL+F1 hotkey, simulating the LOAL (Lock After Launch) mode in real life.

 

SELECT t2WeaponCodes.ID
FROM lWeaponCode INNER JOIN t2WeaponCodes ON lWeaponCode.ID = t2WeaponCodes.Code
WHERE (((lWeaponCode.Description)="Bearing-Only Launch"));

 

QueryList_HF Sonar

 

simply list the sonar sensor working in High Frequency

 

SELECT t2SensorSearchFreq.ID, lSensorFreq.Description
FROM lSensorFreq INNER JOIN t2SensorSearchFreq ON lSensorFreq.ID = t2SensorSearchFreq.Freq
WHERE (((lSensorFreq.Description)="HF Sonar")) OR (((lSensorFreq.Description)="MF Sonar")) OR (((lSensorFreq.Description)="LF Sonar"));

 

(note the multiple conditions in the "WHERE" line )

 

 

QuerySubPassiveSignature

 

simply listing the Subs' passive sonar signatures

 

SELECT t2SubCrossSections.ID, t2Sub.Model, t2Sub.Name, t2Sub.Type, lCrossSection.Description, t2SubCrossSections.Front, t2SubCrossSections.Side, t2SubCrossSections.Rear
FROM t2Sub INNER JOIN (lCrossSection INNER JOIN t2SubCrossSections ON lCrossSection.ID = t2SubCrossSections.Type) ON t2Sub.ID = t2SubCrossSections.ID
WHERE (((lCrossSection.Description)="Passive Sonar"));

 

QueryPlanesSignatures

 

simply listing the complete, unlike the request above, signature (Cross Section's Radar, Visual and Infrared values) of all planes

 

SELECT t2PlaneCrossSections.ID, t2Plane.Name, t2Plane.Model, lCrossSection.Description, t2PlaneCrossSections.Front, t2PlaneCrossSections.Side, t2PlaneCrossSections.Rear
FROM t2Plane INNER JOIN (lCrossSection INNER JOIN t2PlaneCrossSections ON lCrossSection.ID = t2PlaneCrossSections.Type) ON t2Plane.ID = t2PlaneCrossSections.ID
WHERE (((lCrossSection.Description)="Visual")) OR (((lCrossSection.Description)="Infrared")) OR(((lCrossSection.Description)="Radar"));

 

cheers,

 

Jan

[JanMasterson]

hello Pooners,

 

here's a very simple request but that can safe your life when your are playing an game with weapons that you don't know:

 

QueryList_WeaponsLaunchParams

 

SELECT t2Weapon.ID, t2Weapon.Name, t2Weapon.Designation, t2Weapon.MinLaunchRange, t2Weapon.MaxLaunchRange, t2Weapon.MinLaunchSpeed, t2Weapon.MaxLaunchSpeed, t2Weapon.MinLaunchAlt, t2Weapon.MaxLaunchAlt, t2Weapon.TextRef
FROM t2Weapon;

 

cheers,

 

Jan

[JanMasterson]

here is a series of request that combine to finally obtain a "Fuel Range check" sheet. One still have to export it it excel and create the formulas to calculate the fuel range and then compare it with the weapon's range but, well, at least all figures are centralized on one single sheet.

 

 

QueryList_WeaponEngine

 

SELECT t2Weapon.ID, t2Weapon.Name, t2Weapon.Designation, t2Weapon.MaxLaunchRange, t2WeaponEngines.ItemID
FROM t2Weapon INNER JOIN t2WeaponEngines ON t2Weapon.ID = t2WeaponEngines.ID;

 

 

QueryList_WeaponEngine_CruiseSpeed

 

SELECT QueryList_WeaponEngine.ID, QueryList_WeaponEngine.Name, QueryList_WeaponEngine.Designation, QueryList_WeaponEngine.MaxLaunchRange, t2PropulsionAltSpd.Speed
FROM t2PropulsionAltSpd INNER JOIN QueryList_WeaponEngine ON t2PropulsionAltSpd.ID = QueryList_WeaponEngine.ItemID
WHERE (((t2PropulsionAltSpd.Throttle)=2));

 

(Throttle 2 is cruise speed)

 

 

QueryList_WeaponEngine_Speed_Fuel

 

SELECT QueryList_WeaponEngine_CruiseSpeed.*, t2WeaponFuel.ItemID
FROM t2WeaponFuel INNER JOIN QueryList_WeaponEngine_CruiseSpeed ON QueryList_WeaponEngine_CruiseSpeed.ID =  t2WeaponFuel.ID;

 

 

QueryList_WeaponEngine_Speed_Capacity

 

SELECT QueryList_WeaponEngine_Speed_Fuel.ID, QueryList_WeaponEngine_Speed_Fuel.Name, QueryList_WeaponEngine_Speed_Fuel.Designation, QueryList_WeaponEngine_Speed_Fuel.MaxLaunchRange, QueryList_WeaponEngine_Speed_Fuel.Speed, t2Fuel.Capacity
FROM t2Fuel INNER JOIN QueryList_WeaponEngine_Speed_Fuel ON QueryList_WeaponEngine_Speed_Fuel.ItemID = t2Fuel.ID;

 

cheers,

 

Jan

[TonyE]

First minimally operational version for ANW 3.10.1 has been released (see first post in thread for link).

 

o 2011.01 2011/11/09

 Blatantly copied swaths of code from the RE with AGSI’s permission so that the import process will function again.

 Picked and chose other chunks of code and modified some by hand for import.

 Made the minimum necessary table structure changes to allow import of the ‘old’ database.

 Work done against H3RE_3_10.mdb

[TonyE]

o 2011.02 2011/11/17

 Weapons comparison should be done

• Added Comparisons for

o MaxTargetAltitude

o MinTargetAltitude

o AirThreat

o SurfaceThreat

o SubThreat

o StrikeThreat

• Adjusted field sizes to match the RE (converting some integers to doubles, singles to doubles, etc.)