User Group Permissions & Jump Menu

I have 4.0 build 79 . I am testing and noticed that the new option group id in the permission area ; is causing a problem with my project . I have the user logins set to view and edit own data . Then I have group permissions set for specific users to access this data based on a field in the users table. When the user trys to login ; I get a message; ( user does not have permission to access this page ; back to login page. ) I see that there is a new option in the user permissions setup for group Id. When I try to change the group Id to the users Id field and save ; it reverts back to the Id field of my users table key field ; which is not the users Id field and hence the (do not have permissions message.) I tried this several times and the group id field just reverts back to the Id field. Am I missing something or did the way permissions are used change in this part of asprunner . I did not have this problem with user group permissions in the last version 3.

Update to this . After Further testing with a new project ; the group id field does what it is designed for. My question now is can you use old projects with the new version of 4.0 ; because in testing with a prior version project ; the group permissions fail to show group users the menu; whereas in the new version on a new project the permissions are correct . This is my first cross-over from one version to the next ; I was under the assumption that projects created with old versions would normally be valid.

John,
let me explain how it works.
ASPRunnerPro 3.2 didn't have a separate field to store GroupID. We used username field for this purpose.
When you open old project file in ASPRunnerPro 4.0 it assumes Username field becomes GroupID field keeping existing user groups. Technically speaking you can open existing project in ASPRunnerPro and just build the code.
Let me know if it doesn't work as expected.

The Group Id field ; seems to be using the username to give permission. My Problem was my old project which is fairly large ; uses a seperate field in that same record to authenticate that this is the user of a certain group which in turn can see the menu and have access to certain and only that groups records. To do this I have a field with certain clubId# assigned to these group users. Because the group Id field is being used ; which I used before in older version ; the users are no longer having access to the menu because it is identifying the user id as the key to the permissions table ; which in turn uses a ID# to identify the records that they have acces to and the menu ; which makes each user a unique permission and does not match the ( Users Table field ) against the ( Main Table Field. ) . This is only happening with older projects and works fine with new projects in 4.0. I am in the process of re-writing the entire project over but am concerned about the change that was made and that it could affect the project later. Seems to me that there is something in another part of the new version that is checking the (users table) against the group Id# . If I'm wrong then my project must be corrupted. The only other change I made was a template change as old templates do not work with the new version. I then tested with a default template and the old version ; still same problem. Thanks for your feedback . Love the product and I;m learning new options I have with it everyday.

John,

John,
I'm still confused.
Is it a problem with old to new project conversion or just a problem with new version?

John,

Problem started after 4.0 install with templates other than the default template and both old version projects and new projects.
It seemed that my groups were not being authenticated correctly. After further testing ; I used one of the numbered templates ex. Template 1 ; and same problem ; no access to the menu. Now when I use the the default template in the new version ; the menu shows and seems to be authenticating users correctly . Seems my templates were corrupted. The only template that works seems to be the default template. Will have to test more templates as ; I am now just using just the call headers and footers . not sure why templates had an impact on the menu showing or not showing the menu options; just showed username and logout instead of the menu options ?

John,
old templates won't work with ASPRunnerPro 4.0.
If you use templates created by older version this means you simply missing some functionality that didn't exist in old templates.