Esbjörn, The SYS_PASSWORDS table is a hidden table. You can see the table during a reload. You won't see a change in the DB size unless you perform a RELOAD after the PACK PASSWORD. When I initially performed the reload I noticed that the SYS_PASSWORDS table was HUGE. I would like to know what causes the table to get so large. In my case, I have been adding tables to the database and have been using a stored procedure to refresh access rights. I suspect that my "refresh access right" routine may be the culprit. I will do some testing when I have a chance.
John -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Esbjörn Johansson Sent: Friday, February 01, 2008 7:03 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: SYS_PASSWORDS Hi all A. Razzak Memon wrote: > Use PACK PASSWORD command to clean out bogus rows from SYS_PASSWORDS > table. This was interesting, as was the differing views on grants versus no grants. I just checked one of my databases - there was NO sys_passwords table! In this db there is an owner and grants to a number of users. So I did a "list access for .." one of the users and noticed some incomplete rows in the list. I then did a "pack password" - got no change of size for any of the db files but the incomplete rows were gone when I did a new "list access for ..". We handle this database with separate "SET USER .." and "CONNECT dbname" and never use "CONNECT dbname IDENTIFIED BY username password". I have the impression that there are two different internal mechanisms handling these security functions. I would like to know more about these differences. Esbjorn
