639
Has anyone run across an instance where the PV lists are blank but you can type the value in the field and it populates? For example, in the User Maintenance screen, I can't see the user but I can type in their name to see the groups they have access to. The client is using windows authentication.
*This post is locked for comments
There ended up being Userrec and Grprec tables in the appdb so it was looking there, not in the system db. Renamed the tables in app db and everything went back to normal.
Not sure how those tables got in the app db though.
Thanks for all your suggestions!
It still does not make sense. Here is the PV behind the user ID field on the user maintenance screen.
CREATE PROCEDURE
sm_UserRec_UserId
@parm1 varchar(47)
AS
SELECT
*
FROM
UserRec
WHERE
UserId LIKE @parm1
AND
RecType = 'U'
ORDER BY
UserId
From this you can see the only criteria is that the rectype equals U. That table should only have values of U or G in that field and I suspect you have already checked that out. If this were some sort of SQL security issue then you would not be able to open that table at all. As far as I know, there is no record level access control in SQL. And, as you said, the missing user IDs are in the table and, if you enter that ID, the screen populates. Unless there is some sort of restriction logic in the actual screen code that we do not know about, it should be working.\
One thought, when you query the userrec table, order by userid and see if there just might be extra characters or even blank userid records in that userrec table such that the missing names are actually there in the PV list but not in the order expected.
All those PV's you mention are linked to the System Database, where the SQL Procs that populate the PV's are found. Does this happen for all users, including SYSADMIN, or just some users? Wondering if you have some user security issues in SQL that are restricting certain access to the system db for users?
The issue seems to only be with the user maintenance, group maintenance, access rights maintenance and the menu maintenance screens. When you F3 on the user id or group id field, you see a partial list however, all the users and groups are in the tables when queried via sql.
If I'm in the user maintenance screen and want to see which groups the user is assigned to, I can type in the user if it isn't listed in the PV list and the screen will populate. However, if I go to the group tab on the screen and see the new group I created but F3 for the PV list, the group doesn't appear in the list.
Does this make more sense?
Is this happening only on those screens or any SL screen? When you say the list is incomplete do you mean it shows some of the users or groups but not all? I am trying to get a handle on the exact situation. As described, it sounds strange in that the PV list is populated by the pvrec command and the corresponding stored procedure behind the field. The screen is going to run the equivalent of a pvchk against the results of the pvrec and is not going to let you continue on populating the remainder of the screen with the data record unless it finds that userid or groupid. Now, if it does not find it, the screen should then assuming you are adding a new record and will let you continue but it will not display any content in the other fields. So, I am looking for a more detailed description of what is actually happening. If the pv list is partially populated then I do not see how it could possible be an ownership issue on the database.
You have me a bit stumped with this issue but I am willing to work it some more if you can further describe the events.
Of course, if someone else has any ideas on this, please chime in.
What is happening is when I go to lookup a user or group in Administration, the lists are not complete. If I type in the user or group, I'm then able to proceed forward. I have seen this happen once before with PO numbers and we had to set dbo as the owner of the database. Do you think this may be what is happening since synchronizing the database and updating the PVrec didn't seem to help.
Cherie
I cannot tell for sure based on how you wrote this item up but here are some thoughts.
If you can enter the value in the field and not get an error about the item not found then your PVRec and PV are working.
This could be an enter =tab issue perhaps related to this user. go to the tools and make sure enter = tab while logged in as this user.
I ran the update database and ran pvrec again without any difference. Any other thoughts/ideas?
Have you tried running Database update and reloading PVRec.csv? (In the \db\csvs folder in your SL install)
Share
Report
All responses (
Answers (
