this sometimes comes up for us when developing, but should not happen for users. is there anything unusual you did with vizzie that you can think of?

you can likely fix this via a database reset, but putting "; max db.reset" in a message box (without quotes) and clicking on the message. then restart max (the database will have to rebuild, which will take some time).

Okay, thanks Rob. The max db reset fixed the issue. Thanks! I haven't touched Vizzie, so not sure why. Still getting up to speed with new Max features. I do have a lot of old 32 bit externals though.