Ok. I have never come across this problem before. I am setting up separate menu files, e.g. AR_MENUS and AP_MENUS. In setting up these menus, I call other menus, i.e. @AR_MENUS@INVOICES.

When I use the menus and choose a menu option, e.g. INVOICES, the sub menu appears, however if I return to the main menu and reselect the INVOICES menu option, I get an error message stating the "Menu INVOICES has not been created."

Obviously it has since I can view it initially, but not afterwards. If I reset (attachtables) the sub menu appears for one time and then I get the above error message.

This happens only when I am selecting a menu from another file other than the MENUS file. If I enter INVOICES in the command column (indicating that it is from the MENUS file), then there is no problem. I also have used @MENUS@INVOICES and there is no problem. Only if I have @AR_MENUS@INVOICES do I get the error message.

Any suggestions?

Frank

Frank,

My first, and most obvious, thought is that you are somehow detaching the AR_MENU table/volume somehow. Or perhaps you are attaching an older version of this table in a different volume.

[email protected]

SRP Computer Solutions, Inc.

Are you doing this in R/BASIC code or using a Catalyst Code / Command sequence? If R/BASIC, make sure that there are no bugs in an ATTACH / DETACH sequence. Are all the Menu files marked GLOBAL rather than the account(s)?

FWIW, I don't usually have separate MENU files, althoough I do use separate TEMPLATE files and execute the appropriate template depending on the USERNAME and associated privileges. Some are completely open, others are read-only, and others are selectively enabled. That's a different kettle of fish.

The error you're getting seems to be associated with an ATTACH / DETACH issue, though.

Don Miller

C3 Inc.

I'm not using RBasic, merely using a Catalyst Code / Command, i.e. M / @AR_MENUS@INVOICES

At the present all menu files are on the default account. I am planning to move them to individual accounts, but not until later.

I haven't separated Menu files until recently because I want to package the application into individual modules, i.e. AP, AR, GL, etc.

]]The error you're getting seems to be associated with an ATTACH / DETACH issue, though.«

Agreed, but the question is why? As soon as I reattached it works fine for one try, then …

]]My first, and most obvious, thought is that you are somehow detaching the AR_MENU table/volume somehow. Or perhaps you are attaching an older version of this table in a different volume.«

I agree, but why? Although I plan to separate the menus to different, appropriate accounts, they are all on the same default account at this time.

I should have no problems simply because all the menus are currently on the same, default, account, but …

It's very odd

One final point. Even when I access the menu and receive the error message, I can do an edit and view the menu in the edit mode. This seems to indicate that the issue is not an attach/detach issue, but an issue in how the menu is deciphering the menu option.

View this thread on the forum...