Zugg Software :: View topic - [3.10a] Importing Map Pulls The Wrong File

Novice Joined: 29 Jan 2006 Posts: 40 Location: Aardwolf

I have a saved map with a name like mudmap.dbm. We share this map between a lot of people, but make changes in the ZMud version since it's apparently too much trouble for CMud to be able to export an mdb. I downloaded a new version of the mdb map named mudmap.mdb. With .dbm open in CMud, I go to File and Open, then select "Old Mapper Files" and select the .mdb file to convert it since it's newer, however the next dialog that pops up says "Opening map mudmap.dbm". It would seem that if you have two files with the same name but different extensions, CMud is grabbing the dbm.

Novice Joined: 29 Jan 2006 Posts: 40 Location: Aardwolf

Changed the name of the newer file to mudmap2.mdb and it imports properly.

Novice Joined: 29 Jan 2006 Posts: 40 Location: Aardwolf

Now the conversion has failed with an Access Violation. Getting kind of ridiculous. ;)

ZoneTreeTbl: Cannot perform this operation on a closed dataset.

Novice Joined: 29 Jan 2006 Posts: 40 Location: Aardwolf

To verify I reinstalled 3.08 and tried to convert the map again. It seems to go a lot slower than what I was seeing in 3.10a, but it worked perfectly, and all the changes that were made are there and appear to be correct.

Wanderer Joined: 02 Sep 2005 Posts: 85

I'm getting this error, as well. (3.10a) and yes, I'm running windows 7 RC with latest patches

Posted: Thu Oct 08, 2009 4:48 pm

Yes, I can see the bug where CMUD will grab the *.DBM file if it has the same name as the *.MDB file. The internal MapOpen routine does this automatically to be sure that the newer DBM file is loaded rather than the old MDB file. I'll try to change the File/Open option so that it tells MapOpen not to do this automatically.

However, do you still get a failure with the renamed map file? If you have a *.MDB file that is not converting properly in v3.10 when renamed, please email it to me ASAP at sales@zuggsoft.com. I haven't seen any failures with any of my MDB files here, so there is no way for me to fix this bug without an example map file that shows the error. But it's very possible that the speed optimizations done in the 3.10 conversion have resulting in a problem in some cases, so it's very important that I get your map file to test this.

Also, CMUD will never be able to *export* an old MDB file. The whole point of the 3.x version of CMUD is to get rid of the Microsoft ADO/MDAC format dependence (which is what the old MDB file is). Also, new features being added to the mapper do not allow compatibility with the old format, so exporting to an old MDB file would lose map information. It's the new DBM format that will allow the new mapper to finally move forward and start having the new mapper features that people have wanted for years. It's just like how newer zMUD versions are not able to export the really old *.MAP map files.

Sorry this means the new CMUD maps are not useable in zMUD, but once CMUD 3.x is a Public version, then you should be telling friends to use CMUD and not stick with the 5-year old zMUD.