Matrix Games Forums

ORIGINAL: iriyak

Finally figured out the record in PDb. The VBA engine stopped processing while attempt to commit the record set for the platform named "ans Beimler Hans Coppi Heinz Ka". It belongs to "Germany DE / FRG / DDR".

[SNIP]

I have no idea why only in my environment this runtime error happens, but similar to "Air-Sol Moyenne Port^e Rkt".

I am wondering if you might be experiencing some data corruption.

I looked at entry #400 for the HUD3 and it is named, "Air-Sol Moyenne Portée Rkt". Entry #400 in the PlayersDB is for the same weapon because we built the PlayersDB using HUD2 as the basis even though we named it, "ANS Rocket".

I used the HexEditor to look into the Propulsion.DAT files for both the HUD3 and PlayersDB but could not even find the words "Beimler Hans Coppi Heinz Ka". I really do not know from where they come

It does seem as though the problem is centred on your Propulsion.DAT, though. Perhaps you could try to manually Import that specific annex and see how that works. Also, there is supposedly a "Compact and Repair Database" command that may help. TMC told me that you can find it under, "Add-in ==> tools ==> Database Utilities ==> Compact and Repair Database"

Hi Herman,

ORIGINAL: hermanhum

ORIGINAL: iriyak

Finally figured out the record in PDb. The VBA engine stopped processing while attempt to commit the record set for the platform named "ans Beimler Hans Coppi Heinz Ka". It belongs to "Germany DE / FRG / DDR".

[SNIP]

I have no idea why only in my environment this runtime error happens, but similar to "Air-Sol Moyenne Port^e Rkt".

I am wondering if you might be experiencing some data corruption.

I looked at entry #400 for the HUD3 and it is named, "Air-Sol Moyenne Portée Rkt". Entry #400 in the PlayersDB is for the same weapon because we built the PlayersDB using HUD2 as the basis even though we named it, "ANS Rocket".

I used the HexEditor to look into the Propulsion.DAT files for both the HUD3 and PlayersDB but could not even find the words "Beimler Hans Coppi Heinz Ka". I really do not know from where they come

It does seem as though the problem is centred on your Propulsion.DAT, though. Perhaps you could try to manually Import that specific annex and see how that works. Also, there is supposedly a "Compact and Repair Database" command that may help. TMC told me that you can find it under, "Add-in ==> tools ==> Database Utilities ==> Compact and Repair Database"

Thank you for your comment and checking data on both HUD3 & PDb! OK, I will try to manually import that specific Annex and see how that works.

Just for the record, I summarized when the VBA engine stopped processing through testing results of the second test cycle.



Best Regards,
Kazunori Iriya

PS While finding out the record which stopped processing, I didn't look into the *.dat file. Instead I tried finding it out in putting my debugging code into the relevant VBA module of the mdb. Binary Editor was used because it was figured out the data in the log contained a special character inside. Sorry for confusing you in my description.

Edit: Added PS.

I played around the HCF import and it looks like the Propulsion annex is what is causing the failure. Any annex without a propulsion (Comm, Sensors, warheads) will import. I hope this helps with debugging the editor.

[Deleted by Admins]

More of the same unsupported nonsense:

ORIGINAL:  VCDH

I tried it on both my laptop and the ships network.  No problems here.

How about actually testing a suggestion before throwing it out there for others?

Hi all,

Thanks for the info, I will try that to go way forward.

BTW, Herman, I'm having a fun time to debug so that's no problem [:)] for me at least. I joined the forum about one hear ago and I spent most of time to read articles wondering about when I could contribute to this community. And now I'm happy to know that the time has come.

Best Regards,
Kazunori Iriya

Did you finally manage to work through or around your Import problems?

Hi Herman,

ORIGINAL: hermanhum

Did you finally manage to work through or around your Import problems?

I'm now trouble-shooting the incident on the customer's site in real life. [8D]

So, I will come back to H3ANW soon later!

Best Regards,
Kazunori Iriya

[Deleted by Admins]

ORIGINAL: VCDH

So I'm a liar now?

The results speak for themselves, since everyone else who used the same editor ended up in a crash while trying the Import or Export command.

Obviously, turning on the power is about the extent of testing conducted. (Which is about par for ANW).

Herman, please stop trolling.

Thanks,

The Validation command for the magazine table uses improper logic, IMO.

When the command is given, it calculates the maximum possible number of weapons for a magazine and assumes that this should be the capacity of the magazine. Therefore, if a magazine consisted of two weapons record entries:

Torpedo1 6/12
Torpedo2 6/12

the H3RE would estimate that the maximum capacity of the magazine should be 24. This is wrong since the total magazine capacity of this submarine example should only be 12. A scenario designer could switch weapons around and load a combined maximum of 12 weapons into the magazine.

As well, the Magazine Weapons Records must have some empty 'space' so that a player can unload weapons that may already be loaded into the tubes.

If the weapons records were:

Torpedo1 6/6
Torpedo2 6/6

the current loads in the tubes would have no place to unload in order to switch to a different weapon.

The H3RE is also inconsistent with the H3Editor. When doing a Sanity Check using the H3Editor, it evaluates using the largest potential record in the magazine. For example, if a magazine had the following two Weapons Records:

Torpedo1 6/6
Torpedo2 6/12

the H3Editor would check to see if the magazine capacity was at least 12 (and not 18). I believe that this logic is more proper.

Dale,

The test I did was try to export a propulsion file from database that I know working (HUD3 & ANW). The import of the HCF file failed on any random record. Stating too few parameters. Let me know if more information is needed.

The issue was caused by the renaming of some propulsion fields and not updating a query used in the HCF export process which uses those propulsion fields.

It's fixed for the next release.

Question, what do you use the HCF files for? Was it for debugging other issues? Just curious.

Thanks,

I was just playing with all the features of the editor and ran into this error. I just want to let you know what I found. In the past I used it to export and import my own units into databases.

[Deleted by Admins]

Hi all,

ORIGINAL: iriyak

Hi Herman,

ORIGINAL: hermanhum

Did you finally manage to work through or around your Import problems?

I'm now trouble-shooting the incident on the customer's site in real life. [8D]

So, I will come back to H3ANW soon later!

Best Regards,
Kazunori Iriya

A quick update: I tried importing with MS Access 2003 SP2 & HUD3 (June 12th 2009) over Vista Enterprise English edition, yet another PC. The RE imported without stopping processing!

The below screenshot shows the 400th record was successfully imported into the database. You can see a Japanese character in Name field and I believe it is because of the font setting in it.



My first environment was Japanese edition and this might cause the unexpected VBA engine's behavior related to reading or parsing strings over .dat file. It will be verified later.

Best Regards,
Kazunori Iriya