Thanks Javier, Yes, I've tried those but my problem is trying to get NO password:
If I recreate all 5 of my databases which all use the same owner and logins and start with: CREATE SCHEMA AUTHORIZATION Books XYZ and then unload the structure I get: CREATE SCHEMA AUTHORIZATION Books XYZ SET USER XYZ none I then cannot connect as the owner unless I enter the password as "none" whilst other user names are okay (it seems). If I create a new database with a different owner, say ABC and no password, I get the single create line as expected when I unload. I've not finished playing yet but it _looks_ as if R:Base knows there are other similar user logins and cannot accept different passwords for them - which is not unreasonable if that were the case but it's not in Razzk's FTE article on the subject. Another weird thing is that sometimes I can use my owner name without having to enter the password - maybe when no database is connected when I set the user and then connect to the database - I need to investigate this further... I need also to try recreating the 5 databases all with different owner names and see if that stops the additional set user line and then, if it does, try changing the owner names back to the one I want. Regards, Alastair. On 30/01/2017 22:30, Javier Valencia wrote: Alastair, This are the command I use: If your database does not have an owner then: RENAME OWNER PUBLIC TO NewOwner To add a password use: SET USER PASSWORD FOR NewOwner TO NewOwnerPassword It seems to work for me. Javier, Javier Valencia, PE 14315 S. Twilight Ln. Olathe, KS 66062 Home: 913-397-9605 Office: 913-829-0888 Cell: 913-915-3137 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Alastair Burr Sent: Sunday, January 29, 2017 6:57 AM To: [email protected]<mailto:[email protected]> Subject: Re: [RBASE-L] - View: Union / Group By - cannot see what's wrong Thanks, Javier, Yes, that makes sense even though I checked "everything" "thoroughly" - it's easy to see what you want to see and not what is there these days. I will check it and can do so quite easily simple by removing the aliases in one fell swoop. If the view then works I know where the problem is - I just have to find it. However, having got it working I have another problem which I want to resolve first: As intimated in my reply to Razzak, I suspected that the view problem was linked to a grant permissions problem. With the view working that problem has all but gone away - obviously good - yet I still have a problem with users and passwords. As a single user I use four logins simply to create different menus: Public (view only); ADBB & Alastair (edit, 2 for the rare occasions I need multi-user) and Owner (everything including delete just to make me more careful!) None of these users has ever had a password. I select the user from a choose and just type the name to gain access. I cheat with the Owner selection by knowing it is a different name to type so that typing ADBB will get me in but typing Owner won't. It's secure enough for me as nobody else in the house uses the computer. The problem that I have now is that, somehow, R:Base seems to think that there are passwords and nothing I do seems to clear them. Even an unload/load where the database is recreated with CREATE SCHEMA AUTHOR Records XYZ does not clear the problem for me. I have tried SET USER XYZ PASSWORD 1234 but the command "appears" to be ignored. What I want to do is set the password to nothing - I've tried NULL, -0-, '', ``, ` ` (18 spaces) but no luck so far. I now presume that R:Base stores usernames and password combinations somewhere other than in the database - not unreasonable if so. Regards, Alastair. On 28/01/2017 17:35, Javier Valencia wrote: Alastair, I believe Stephen is on the right track. One way to check is to start adding (or subtracting) columns one at the time, when you add (or subtract) the column that is creating the problem the error will show (or disappear if subtracting columns) and that should give you the name of the column creating the issue and you can investigate further if it has a different definition on an existing table or perhaps on another active view. Javier, Javier Valencia, PE O: 913-829-0888 H: 913-397-9605 C: 913-915-3137 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Stephen Markson Sent: Friday, January 27, 2017 1:13 PM To: [email protected]<mailto:[email protected]> Subject: RE: [RBASE-L] - View: Union / Group By - cannot see what's wrong Alistair, if the COLCHECK setting is solving the problem, that may indicate that one of view column aliases is the same as a column name in some other table with a different datatype. Regards, Stephen Markson The Pharmacy Examining Board of Canada 416.979.2431 x251 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Alastair Burr Sent: January-27-17 12:52 PM To: [email protected]<mailto:[email protected]> Subject: Re: [RBASE-L] - View: Union / Group By - cannot see what's wrong Thank you very much, Razzak, setting ColCheck off did the trick. I notice that if I turn ColCheck back on I immediately get the error message again as soon as I try to use the view. I have looked at the names in the view almost endlessly today to try and see where the error was so I am puzzled as to where R:Base finds a difference. I think I would rather correct that than run with ColCheck set off all the time. Obviously I can change the setting in a command file before and after use but what has raised this problem is the error message is received whenever I reconstruct the database from unloads. (But not with Reload.) This may be a complete misinterpretation but I also have a suspicion that this particular error has been causing problems with my user privileges. Is that possible? If so, I may have to run with ColCheck set to off all the time. With that in mind when was ColCheck introduced and/or was it changed with the upgrade to v10? Again thanks, Regards, Alastair. On 27/01/2017 16:38, A. Razzak Memon wrote: Alastair, A few questions ... 01. What is the COLCHECK setting? SHOW COLCHECK 02. What results do you get when turning OFF the COLCHECK setting. SET COLCHECK OFF FYI, COLCHECK ON setting checks the consistency for column names and data types when making views. Hope that provides you with some blue's clues ... Very Best R:egards, Razzak. At 11:24 AM 1/27/2017, Alastair Burr wrote: I know it's Friday but can anybody see what's wrong with this view (an image so that hopefully the email system doesn't mangle my layout): If it hasn't, there should be 6 columns so that I could see the columns and data types (first 5 rows remmed out) more easily. I am not sure that I am defining the time entries correctly - I've tried with as well as without quotes. I am pretty sure I have the data types right - despite the error message. I am not sure that I have the group by right. I only really need to group by: T21.Concert_Date, T22.Full_Name, T23.Full_Name (date, venue name & artist name). [] -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
