[Mobhack]

Originally Posted by DRG

This will not open in Excel and I'm not the least bit interested in DLing a "free" program that forces me to "Get 3 Years Unlimited Software Download & Support ONLY $11.98/year"

So the only two alternatives are post any hard data inconsistencies you find on the forum( variations on HEK or accuracy etc etc for one weapon ) or find some way to convert this to something that can be read by Excel.

Don

The Open Office suite can save to Word format, so probably can handle XLS. It may even be a form of .xls Don's Microsoft Excel might be able to read !

It can definitely read .xls files - I have the thing on my netbook, which is languishing since its touch-pad went wonky.

The Original Poster should really explore the File->Save As dialogue of the thing. Save as the oldest version of Microsoft Orifice file you can get away with, and you are more likely to have end users able to read your files. (Excel 95 say), or .csv as that is universally portable (and Excel reads it too !

Meanwhile I'l continue with the paradox database and SQL like

Select U.NationID,N.NationName,U.name,U.slot,u.SteelHullf ront,
u.steelhullside,u.steelhullrear,u.steelturretfront ,u.steelturretside,u.steelturretrear,u.steeltop
FROM Units U, NationNames N
WHERE( LOWER(U.name) LIKE "%zsu%%23%")
AND U.nationID=n.nationID
ORDER BY U.Name

Which lets you compare the armour suite of the zsu-24s in the game - but like all checking, the cases where some nation has it renamed to a "zing ping 4A2M234" won't get picked up by such a query...

so you end up with carp like:

Select U.NationID,N.NationName,U.name,U.slot,U.unitclass, u.graphic
from Units U, NationNames N
where
( ( LOWER(U.name) like "%152%")
OR (LOWER(U.name) like "%2s%%3%")
OR (LOWER(U.name) like "%Ak%")
OR (LOWER(U.name) like "%sau%")
OR (LOWER(U.name) like "%1973%")
OR (u.graphic=37) )
AND U.nationID=n.nationID
AND ( u.unitclass=21 or u.unitclass=130)

which zeros in on some variations of the SO-152 SPH (and gives some noise as well.. While still having the initial simple query's problem that if you did not know there was a variant called a "Ping Pong 66" then it wont be detected .)

With SQL queries we can check a lot of things - but first we need to know the problem is there and what prcisely to look at.

Andy