I've not used v7 much (just playing around), but I know that I've had problems before with setting preferences, and the current user logged in didn't have access to the ar.ini file, so the preferences kept getting reset.
Make sure the user you are logged in to windows as has permissions to the proper file that stores the table preferences (whatever file that is). HTH -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Heider, Stephen Sent: Monday, June 25, 2007 9:56 AM To: arslist@ARSLIST.ORG Subject: Re: Table Field Columns Not Visible Getting closer... The User Tool is 7.0.01 p2. When I right-click on the table field and select Reset all columns appear. When I logout and log back in those columns are not visible. When I login on another computer with User Tool 6.03.00 p16 all of the columns appear. How can I get the columns to remain visible in User Tool v7 without having to right-click and select Reset each time the form is opened? Stephen -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Mike Wallick Sent: Monday, June 25, 2007 10:42 AM To: arslist@ARSLIST.ORG Subject: Re: Table Field Columns Not Visible I've also seen this when using the v7 user tool. Since that version allows users to specify table field preferences (like showing/hiding table columns), I've noticed that when I add columns to a table field and then open that form in a v7 user tool, I have to "add" the column by right-clicking on the table, choosing preferences, add column, etc. However, since you're using WF to show/hide these columns, that's probably not the issue. Again, if you're using a v7 user tool, you could try resetting the table (right click on the table, choose preferences, reset. That will reset any client-side table field preferences. Just a thought. Mike On 6/25/07, Opela, Gary L Contr OC-ALC/ITMA <[EMAIL PROTECTED]> wrote: > Interesting. > > You said that you did check permissions on each of the columns, right? > Did you check to make sure that the entries in the Group form were in > production too? > > I've noticed before that whenever importing, it will sometimes import > the permission on the field even if I've not yet created the group yet. > > Also, bear in mind, that if you copy/paste a table from one form to > another (for instance from dev to prod) that the field IDs on the > columns in the table are not retained. They will be assigned new > column ids, so if you rely on WF to make the columns visible, this > might be an issue as well. > > The things I would check: > > Permissions on each column > Groups in the group form for the permissions If I'm relying on WF to > make columns visible, make sure there is no issue with field IDs on > the columns Delete all cached views (arv and arf) for that form Check > on the table properties tab to make sure that the column widths didn't > some how get messed up > > I'm wondering if its not an issue with groups, since it works on dev > but not production. I've had this exact issue before with some fields > on dev showing up, but then they didn't show up on prod. > > HTH > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Heider, Stephen > Sent: Monday, June 25, 2007 9:24 AM > To: arslist@ARSLIST.ORG > Subject: Table Field Columns Not Visible > > List, > > I hope you can help. This issue is on the production server. > > On the main (home) display-only form a table field that is used to > display tickets is not displaying all columns. They all appear on the > development server but not on the production server. > > I have exported/imported the .def file for the form from dev to prod > several times but the columns still do not appear. If it wasn't the > main/home form I would delete it then reimport the .def. > > On one of the columns I removed the permissions, then added > permissions, then saved the form. That column now no longer appears > in the table field. It seems like something is corrupt. > > I even tried adding every permission and also issuing a Change Field > action to force the column Visible (it is not marked as Hidden in the > .def). > > Help! > > Production: > ARS 6.3 p16 > Windows 2003 > SQL 2000 > > Development: > ARS 6.3 p21 > Windows 2003 > SQL 2000 > > Stephen > > ______________________________________________________________________ > __ > _______ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > ARSlist:"Where the Answers Are" > > ______________________________________________________________________ > _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > ARSlist:"Where the Answers Are" > ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
