Thanks I will add those and see what happens. Marc
----- Original Message ----- From: "Alastair Burr" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[email protected]> Sent: Wednesday, December 29, 2004 5:34 PM Subject: [RBG7-L] - Re: Sys_layout3 problems again > Marc, > > I used to have these in my start-up app: > > -- GRANT SELECT ON `SYS_Forms3` TO PUBLIC > -- GRANT SELECT ON `SYS_Reports3` TO PUBLIC > -- GRANT SELECT ON `SYS_Layouts3` TO PUBLIC > > GRANT INSERT ON `SYS_Layouts3` TO PUBLIC > GRANT UPDATE ON `SYS_Layouts3` TO PUBLIC > > I now have only the last 2 lines. Maybe they really do still need to be > there. > > Regards, > Alastair. > > > ----- Original Message ----- > From: "Marc" <[EMAIL PROTECTED]> > To: "RBG7-L Mailing List" <[email protected]> > Sent: Wednesday, December 29, 2004 8:53 PM > Subject: [RBG7-L] - Re: Sys_layout3 problems again > > > > Hi Alastair > > > > I tried that but same thing happens. > > Maybe I shouldn't worry about this, after > > all if I put in the password first I do not get > > the error. > > > > Marc > > > > ----- Original Message ----- > > From: "Alastair Burr" <[EMAIL PROTECTED]> > > To: "RBG7-L Mailing List" <[email protected]> > > Sent: Wednesday, December 29, 2004 12:10 PM > > Subject: [RBG7-L] - Re: Sys_layout3 problems again > > > > > > > From the "What's New" for upgrade #78: > > > > > > The system tables used in 7.x/8.x for Windows (SYS_FORM3, SYS_LABELS3, > > > SYS_LAYOUTS3, > > > SYS_MERGE, and SYS_REPORTS3) will always have SELECT permission, > > regardless > > > of the user. > > > > > > and: > > > > > > When defining a new database, SYS_FORM_NAME, SYS_LABEL_NAME, > > SYS_MERGE_NAME > > > and > > > SYS_REPORT_NAME in SYS_FORMS3, SYS_LABELS3,SYS_MERGE and SYS_REPORTS3 > > system > > > tables respectively are now defined as UNIQUE Index to avoid duplicate > > > entries when using > > > LOAD command to load forms, labels, R:Merge templates and reports in > > 7.x/8/x > > > for Windows. > > > We strongly suggest that you re-build your existing database in order to > > > implement this > > > enhancement. Here's how: > > > > > > DISCONNECT > > > SET MULTI OFF > > > CONN dbname IDENTIFIED BY ownername > > > SET NULL -0- > > > OUTPUT newdb.ALL > > > UNLOAD ALL > > > OUTPUT SCREEN > > > DISCONNECT > > > RENAME dbname.RB? Olddb.RB? > > > INPUT newdb.ALL > > > Be sure to make a good backup copy of the original database. > > > > > > Regards, > > > Alastair. > > > > > > > > > ----- Original Message ----- > > > From: "Sami Aaron" <[EMAIL PROTECTED]> > > > To: "RBG7-L Mailing List" <[email protected]> > > > Sent: Wednesday, December 29, 2004 2:43 PM > > > Subject: [RBG7-L] - Re: Sys_layout3 problems again > > > > > > > > > > Marc - > > > > > > > > Why don't you see if you can replicate your problem by creating a > simple > > > > database in version 6.5 with an owner and then creating the same > > database > > > in > > > > version 7 and see if the access rights are different - and if so, > submit > > > it > > > > as a bug. > > > > > > > > Sami > > > > > > > > -----Original Message----- > > > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Marc > > > > Sent: Wednesday, December 29, 2004 8:19 AM > > > > To: RBG7-L Mailing List > > > > Subject: [RBG7-L] - Re: Sys_layout3 problems again > > > > > > > > Hi Sami > > > > > > > > I did several times, still same problem with the errors and > > > > N's set for select on the sys tables. > > > > > > > > Is it OK that the select value is set to N for the sys tables? > > > > > > > > Marc > > > > > > > > > > > > > >
