Hi all

Need help with a strange issue.  We are currently running both Web and Lan client 7.5.2.  We have an account refference form on both clients displaying data from a table called Z_Account_Ext and the standard Account table.  The Web client displays the data with no issues however the Lan will not display data from the extension table. 

Anyone have any idea's what this could be.

Regards

Andrew James

Edit

I have tried releasing the form again and also changing the field security profile as I seen this on another forum but this did not help
If I log on as admin in the lan client then the data is displayed fine.  Also our test server has no issues displaying the data.

What's the value for SECCODEID in the Extension table? In the Account table?

there are 156 records out of 238547 that do not have the same seccodeids in both the Account and the extension table.  But there is an issue with all the records in LAN
Do you think these 156 records could be causing the issue?

Just checked the Dev server and there are more records that do not match and Dev is working as expected

you need to answer your own question: when is the data not displaying on this form and what are the SECCODEID values for those instances..

You should be logged in as a USER, not ADMIN. Especially in DEV.

Time to check the databindings on the LAN form.

In Dev I am logged in as a user and there are no issues.  The form was bundled from dev and brought into live and logged on as a user in live the data cannot be seen. 

I don't think its the SECCODEID's.  All the bindings are there as well.  Just noticed that on the account details screen we have a 2nd manager field which is brought back from the extension table and this is not displaying either.  However our contact ext and opportunity ext is working fine

Did you bundle over the fields to the Production environment?

If so, your fields are failing Field Level Security due to a known bug in calculating the length of the SEC Profiles Blob. In Production Architect\Admin, database manager Add ONE field to a core table Account\Opportunity\Contact, heck Ticket......we call it FLS, varchar (32).

Then go into FLS and check each profile to make sure it is correct.

Also create a GROUP that displays the extension data and the base table data...that might be useful.

I would also suggest that you use the SLX Profiler to check the Queries that are being generated, then run the queries manually using SQL Management Studio and check if they return the same results as what the SLX Profiler reports.

RJ you are a star.  I created an fls field in Tickets did not work but then created it in the ext table and this resolved the problem

Yep, it is a KILLER. As stated, a known bug.