Re: Message not in catalog -- message number = 9070

2011-01-19 Thread L G Robinson
Hi Folks, Thanks for your continued interest in this thread. I did check the SQL logs to see what happens when I update the User form Password field (FID 102) using the join form with the corresponding field renumbered to something other than FID 102... it does not encrypt the contents,

Re: Message not in catalog -- message number = 9070

2011-01-18 Thread Misi Mladoniczky
-Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of L G Robinson Sent: Friday, January 14, 2011 6:51 AM To: arslist@ARSLIST.ORG Subject: Re: Message not in catalog -- message number = 9070 Hi Folks, Well, I figured it out

Re: Message not in catalog -- message number = 9070

2011-01-18 Thread L G Robinson
Hi Misi, I have not checked the SQL logs but I was assuming (hoping) that since the renumbered password field (on the join form) still maps to the real password field in the real User form (with it's original FID), then it would still be treated as such and encrypted as appropriate. I did in

Re: Message not in catalog -- message number = 9070

2011-01-18 Thread Misi Mladoniczky
Hi, I suspect that if the field id is not 102, it will not encrypt the content before it is sent over the network. The SQL log will still show it encrypted though, as it is encrypted by the server before it is stored. It would be complicated to track the 102 to the actual regular form, as a join

Re: Message not in catalog -- message number = 9070

2011-01-17 Thread L G Robinson
, January 14, 2011 6:51 AM To: arslist@ARSLIST.ORG Subject: Re: Message not in catalog -- message number = 9070 Hi Folks, Well, I figured it out, but I still don't understand why it works the way it does. I created a new regular form and a new join form and I was able to include

Re: Message not in catalog -- message number = 9070

2011-01-14 Thread L G Robinson
not in catalog -- message number = 9070 : 104, 9070, NCSUUsers NCSUUsers is the name of the join form. It appears to be something specific about 104. If I change the field id before saving the form, it will save but of course, then the field does not display correctly. It displays the group id number

Re: EXTERNAL: Re: Message not in catalog -- message number = 9070

2011-01-14 Thread Reiser, John J
: EXTERNAL: Re: Message not in catalog -- message number = 9070 Hi Folks, Well, I figured it out, but I still don't understand why it works the way it does. I created a new regular form and a new join form and I was able to include the Group List field from the User form. So that told me

Re: EXTERNAL: Re: Message not in catalog -- message number = 9070

2011-01-14 Thread L G Robinson
Hi John, Apparently, it's a know issue: SW00380659 - ARERR 9070 - Message not in catalog while creating join with the User form I can't see any details on the defect but in my case, I was including several of the special fields from the User form including Login Name, Password, Group List

Message not in catalog -- message number = 9070

2011-01-13 Thread L G Robinson
that should prevent me from adding it to the join. If I remove that field, the form will save just fine. Message not in catalog -- message number = 9070 : 104, 9070, NCSUUsers NCSUUsers is the name of the join form. It appears to be something specific about 104. If I change the field id before