Error 3343

You may post here if you are having problems with Winlog32 that others may be able to help you with. You may also report bugs so that the author may act upon them.
Post Reply
Fred
New user
Posts: 0
Joined: Wed Apr 18, 2007 9:24 am

Error 3343

Post by Fred »

Hi all,
After updating a few mistakes in my log (wrong contry codes), it appears that the DXCC database is not recognized anymore...
Oups!!!
WL32 gives me an Error 3343-Unrecognized database format, and then is shuts down.
All other databases looks good (IOTA, WAZ, WAE,...).
I am usig the 5.8.3 version of WL32
I tried the REPAIR option for the current Log&Database, but nothing to do.
I checked with another log I use and all is good.
It looks the DXCC.mbd is corrupted, but how can I restore it?

Any help?

73
Fred F4EOP
Fred
New user
Posts: 0
Joined: Wed Apr 18, 2007 9:24 am

Error 3343

Post by Fred »

Well well well.
I found one solution: re-create the DXCC database.
1-WL32 being closed, renamed the DXCC.mdb file to DXCC.mdb-old
2-opened WL32. Of course, no dxcc data is available.
3-in File Maintenance, Create a New Ancillary Set
4-reloaded my log
5-Lunched LCR from QSO#1
It looks good until now. Still checking!!!

73
Fred F4EOP
G0CUZ
Site Admin
Posts: 461
Joined: Wed Jan 02, 2002 7:12 am

Error 3343

Post by G0CUZ »

Hi Fred

Not sure how the database was corrupted unless you opened it in MS Access or another program.

Otherwise it sounds like you did all the correct things to get going again.

73 Colin
G0CUZ
Fred
New user
Posts: 0
Joined: Wed Apr 18, 2007 9:24 am

Error 3343

Post by Fred »

Thank you for your reply Colin,
As evreything look good now, I can consider the problem is fixed.
However, I did not use any MSAccess or other software to open or modify the database.
If the cause is not identified, there is a solution. That is the most important.

73
Fred F4EOP
Post Reply