Custom Screen Sets Disappearing

[vanessa03]

Macola 7.6.300b SQL 2000- I am having a wierd problem. My custom screen set for a group quit working. I am not sure what I have done to cause this. I had deleted some companies and users, but I don't think this should be a problem. I have removed the users from the group(the screen set was copied to the group), deleted the group, delete the custom screen, rebuilt and to no avail. The screen set works in SQL Explorer, but not in Workflow explorer. Any ideas? Thanks. Vanessa

 

[dgillz]

Is there any reason why you applied this to the group as opposed to making it the default screenset for all users?

Are the other users with access to this screen that use the unmodified screen, or a differently modified screen?

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry

 

[vanessa03]

Yes, Different groups(companies) have different screen sets for the same program. But none of the groups are working and none of the individual users screen sets are working either under Workflow Explorer. They work under SQL Explorer. Thanks for answering.

 

[MacolaHelp]

Did you check the screens database for the custom screen after deleting the group and custom screen set to be sure no "orphaned users" were still attached to that screenset? Then check your PWE tables to be sure there are no "orphaned users" in there. In older versions of macola, the screensets and pwe tabs tables didn't always update in sync with user maintenance performed in the visual menu builder. Did you double check the data sources after you deleted the companies and the sql cfg file in the macola root for the correct # of companies?

What is the symptom that defines "quit working"? Error message? Just getting default screen set? In 76300, the screens changed to incorporate the former Peak Best OE, so if the screens quit working after an upgrade, you will need to rebuild using the vanilla screenset from 300 with spB applied. Updating alone will not apply the necessary underlying changes.

 

[vanessa03]

I ended up calling Macola on this one. Sorry I forgot to post the results. The tech had me run the SQL script in document number 11.284.637. The Syspass table had lost its menu security code. Even though this does not pertain to menu security, but rather screen security it fixed the problem. Thanks for everyones help.