3.10 Feature: H3RE Available to public

[hermanhum]

Followed by:

[TMC]

I am using Access 2007.

[hermanhum]

Are you able to successfully export the Warhead table individually?

[TMC]

No exporting the warhead annex does not export. Complie error Sub or function not defined. Debug take me to WriteInterger 0.

[hermanhum]

Are you able to export any of the other tables individually?

p.s. You many not want to try default directory option.  I found it may cause some grief that went away when I did the export command individually

[TMC]

I never use the default directory option. I confirm that only Warhead annex errors out when export each individual annex.

[hermanhum]

To summarize, I think that:

1) Batch Import was broken (now fixed)
2) Batch Export is broken
3) Warhead table export causes crash

Seems pretty obvious that this editor wasn't even tested once before release if three novice users can find so many bugs on their first runs. [:@]

[rsharp@advancedgamin]

Uploading ... yet another fixed build. This time I downloaded the file and tested (export & import) it with ANWDB, HUD3, and PDB databases in 3.9.4 format.

All went through without error.

http://computerharpoon.com/public/H3RE_ ... 090717.zip

[rsharp@advancedgamin]

Good news that the runtime worked out and I'm curious of any issues that might crop up.

[TMC]

Import and export now works. HCF import still gives a runtime error.

[rsharp@advancedgamin]

Would you give the error? A screenshot or just the text would be great.

Thanks for your time.

[TMC]

I imported the HUD3 database and exported Iowa ship index 1 to a HCF file. I cleared the editor and imported the same file I just exported. I get the following error.

Run-time error '3061': Too few parameters. Expected 8.

Debug send me to this part of the code.

WipeDupes
CurrentDb.Execute "qImport_DupePropulsionFind"
CompareSubTbl "tPropulsionAltSpd", 3

CheckDupes AnnexInfo, rs, rs![Name], "qImport_DupePropulsionList", AnnexInfo.TableName, TempID

[hermanhum]

ORIGINAL: TMC

Import and export now works. HCF import still gives a runtime error.

Concur. Batch Import and Export now works. HCF Import crashes for me, too.

Minor crash due to Text sub-folder absence a default location. Don't know if you want to have the editor more flexible or able to recover from such problems.

Writing Signature... Failure

Don't know if anyone else is experiencing this error message. I am certain that the DBSignature.dll file is at the location specified in the Default menu. Wonder if I am doing something wrongly?

[rsharp@advancedgamin]

The DBSignature.dll file should be in the same folder as the H3RE mdb file. Previous H3REs included it but I missed it on this one.

The Text folder should not be required. I'll take a look at the HCF export process.

Thanks,

[hermanhum]

ORIGINAL: rsharp@advancedgamin

The Text folder should not be required. I'll take a look at the HCF export process.

DB Signature working as directed.

The HCF Export process seems to be okay and completes. The HCF Import process is where we both experienced a crash.

The missing Text folder caused a Batch Export crash when the following options were selected. See image:

[hermanhum]

Not a crash, but possibly an error or fault.

After Weapons.DAT is imported, "Unknown" codes are displayed where no codes previously existed. See image:

[hermanhum]

ORIGINAL: rsharp@advancedgamin

The DBSignature.dll file should be in the same folder as the H3RE mdb file.

This does work, but the Defaults Menu asks for the path to the Detailed Signature Editor.

Is this referring to the DBSignature.dll file or is it something else?

[iriyak]

Hi Russel,

ORIGINAL: rsharp@advancedgamin

Uploading ... yet another fixed build. This time I downloaded the file and tested (export & import) it with ANWDB, HUD3, and PDB databases in 3.9.4 format.

All went through without error.

http://computerharpoon.com/public/H3RE_ ... 090717.zip

Had a progress though it hit runtime error during importing HUD3 & PDb. See attached test results rev.02 in MS Excel format.

Will update you when I finish my investigation in what record VBA engine stopped processing.

Best Regards,
Kazunori Iriya

[iriyak]

Hi Russel,

ORIGINAL: iriyak

Will update you when I finish my investigation in what record VBA engine stopped processing.

Figured out the record in HUD3 at first. The VBA engine stopped processing while retrieving the version for "Air-Sol Moyenne Port^e Rkt" raising runtime error 3421. Confirmed that it successfully processed 399 records before the record.



As remarked for Id.4 in the test report rev.02:

Clicking Debug(D) button jumped to Line# 1191 & Column# 21 of cDATImport Module: ReadLong().

Propulsion Annex indicates the number of records in tPropulsion table is 400. Guess during the 400th record VB engine encounters runtime error 3421.

So I put the debugging code for logging rs![Name] and rs![Version] around Line# 1191 in cDATImport module. Here's the log I take. The log format is tab delimiter plain text where the first column is rs![Name] and the second is rs![Version]. The below snapshot shows how the octet stream looks like around the record in the generated log by my debugging code.



As highlighted in the window, the last octet of rs![Name] is 0x03. I guess the engine seems to advance one more octet to get rs![Name] in my environment, which caused the runtime error 3421: Should have pointed 0x03 as 0x03 seems the version number.

I have no idea why only in my environment this runtime error happens. "Port^e" out of "Air-Sol Moyenne Port^e Rkt" contains some special octet 0xE9 in 0x50 0x6F 0x72 0x74 0xE9 0x65 and it might have caused it, which has to be verified later.

That's all what I've found so far.

Best Regards,
Kazunori Iriya

Edit: Mentioned the snapshot shows for the generated log file, not *.dat file itself.

[iriyak]

Hi,

ORIGINAL: iriyak

Hi Russel,

ORIGINAL: iriyak

Will update you when I finish my investigation in what record VBA engine stopped processing.

Figured out the record in HUD3 at first.

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".

The below snapshot shows how the octet stream looks like around the record in the generated log by my debugging code.



As highlighted in the windows, the name contains 0x0B between r & H and 0x0E between i & H.

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

Best Regards,
Kazunori Iriya

Edit: Mentioned the snapshot shows for the generated log file, not *.dat file itself.