Adding records by Query to an existing DB member

[Guest.Visitor]

In order to add a Physical file member, you must have *OBJMGT authority to the file. If you look at the details of *CHANGE authority, you'll see that it gives you change rights to the data, but not *CHANGE rights to the object. When you query to a new member, you are actually changing the object itself (as well as *ADDing data), so you need object management (*OBJMGT) authority. Do remember that *OBJMGT authority also permits the clearing of file members, so the user will have the ability to clear this file as well. But as it is a query file and not the source data file, it's probably not that big of a risk. jte

[Guest.Visitor]

Adding records by Query to an existing DB member

Thanks John, but we are not trying to add a new file member (Option 3), we just want to add records (selected from a file with an identical record format) to an existing file member (Option 5). Shouldn't rights to the data be sufficient ? Torsten

[S.Mildenberger]

Adding records by Query to an existing DB member

Torsten, Is the query 'adding' records to the file or 'replacing' the records in the file. I believe if it is replacing then it needs authority to clear the file which you can get through the *OBJMGT authority that John mentioned. Scott Mildenberger

[Guest.Visitor]

Adding records by Query to an existing DB member

Is there a higher level of authority then *CHANGE necessary to add records via Query (Option 5 in the QRY-outfile definition) ? One of out users tried this and received QRY5063 (no authority for file ...), but he can write records to the file by using application pgms, which have no authority adopted. TIA

[Guest.Visitor]

Adding records by Query to an existing DB member

If you are not creating a new member, then *CHANGE authority would be adequate. If you're not using Adopted authority on the green-screen applicaiotn that allows the user to update, then there must be another clue somewhere. jte