Zugg Software :: View topic - [3.14] SQL Error: ObjectTbl.Enabled may not be NULL

Beginner Joined: 13 Jun 2005 Posts: 20

I am getting this error when trying to add a new room to a database I converted from 2.37. The database opens fine in 2.37 but after converting to 3.14 I get this error any time I try to create a new room.

I am running Vista 64.

Any ideas/info would be appreciated.

-KF

Posted: Tue Feb 09, 2010 5:54 pm

You need to give us the exact step by step procedure for reproducing this. There are many different ways to add rooms to the map, so we need to know exactly what you are doing.

Also, to determine if this is a problem with your specific map database or not, try the following procedure:

1) Run CMUD, Close the Session window
2) Click the Map button in the toolbar
3) Click the "Map Mode" button in the mapper window toolbar to enable the edit toolbar on the left side of the mapper window
4) Click the square "Add Room" button in the toolbar on the left side of the mapper window, then click anywhere in the map window to add a room

Does that work? If it does, try the same procedure in your own session with your own map.

Also, please send me the crash dump or post it here within [CODE] tags so that we can see the details of the crash report.

Beginner Joined: 13 Jun 2005 Posts: 20

The steps you mentioned are the steps that I followed on my map. On a new map/session it works fine. On the one I brought from 2.37 I get the error mentioned. One thing I tried is opening the map database in a sqlite viewer and removing the not null constraints on the obj table. Once I did that I was able to create a room by clicking on the "Add Room" button and clicking on the map. It still will not automap because it now throws an error on the ExitTbl.DrawRev (I am assuming more not Null fields on a different table). I sent that report this evening.

It looks to me like a problem with the conversion and creating new rooms. When the mapper creates a new room what does it initialize the fields to and how does it get around the not null constraints in the database. Will going through and removing all the not null constraints on all the tables fix my problem (as a bandaid) or will it cause more issues later down the road after I have a lot more hours mapping.

If my map is hosed anyone happen to have a current map of Aardwolf?

Thanks

-KF

Posted: Fri Feb 12, 2010 5:07 am

I got your map file via email and will play with it next week. It looks like a bug in the database conversion. Once this is fixed you should be able to just re-convert your original 2.37 map file, so just keep it handy.

Newbie Joined: 18 Aug 2009 Posts: 1

I got exactly the same error as the previous poster.

If you would like to have another converted / unconverted map database for experimentation, just holler.

M.

Posted: Sat Feb 27, 2010 9:05 pm

I'm getting this same error myself, even with 3.14a. Using the map converter didn't help, either. It's just simply refusing to let me make a new room. Not sure what the problem is. I may wind up downgrading to another 3.xx version, converting the map with that one (since they've worked in the past...) and seeing if it produces the same error.

In the meantime, here's the call stack:

Posted: Sat Feb 27, 2010 9:22 pm

Downgraded to 3.11, converted the map, no issues. It may very well just be an issue with 3.14, maybe even 3.13. I didn't test from 3.12 up because I'm on a crappy connection right now, but if need be, I can do that in about... three weeks. :\

Charneus

Posted: Sun Feb 28, 2010 6:57 am

Yes, it's because of the new map database conversion algorithm. CMUD 3.14 uses the same algorithm that was being tested in the external MapConvert program. Apparently there wasn't enough beta testing of the MapConvert program to find this bug. It's already on the bug list for the next version.

Newbie Joined: 10 May 2007 Posts: 4

I'm on CMUD 3.34, and I haven't been able to use my old maps for quite some time because of the same issues with ExitTbl.DrawRev throwing an error ("ExitTbl.DrawRev may not be null"). I discovered a way to make things work today by loading the dbm file into sqlite3 and manually removing the NOT NULL from the DrawRev column. I don't know whether this will break other things in the future, but for now, it allows me to actually use my maps and modify them.

I'm posting this in case it helps anyone else with the same problem. All you have to do is load up the dbm file in sqlite3 and rename the existing ExitTbl to a temp name. Then create a new table without the NOT NULL restrictions and move all the records over.