Hi,

I just added a radio button to a form and no matter what I do, I cannot get the thing to Enable. I then added a checkbox that is identical as far as the event that fires and the column that gets populated in the table. The checkbox also will not enable! I am pretty new to the world of SLX and development in general, but in this case I am copy/pasting existing code.

The 'Enable' property is checked and the control is visible. On the form it shows as being disabled. I also tried setting the property to enabled via code, but no luck.

thanks for any help you can provide!

It's most likely two things - either the provider has not caught up with the field you added to store this radio button to (did you create a new field?) or, more likely, the security profile is showing this as read only. If you go to Admin, Tools | Manage security profiles and select the read/write one and find your field - is it read/write ? Adjust and restart and you should be fine. Also, what version ?

Hi Mike,

Thank you for your answers. I think this is the 2nd or 3rd time you have helped me (or tried). It didnt work this time. The field in question is one that I created using the DataBase manager. I created a field called 'SDSTicket' (SLX Boolean dt) on the TICKET table. We have created several fields like this over the years on the ticket table and up until now it has worked (the new field works fine in Dev by the way).

I tried the Admin suggestion you had, and the field was Read/Write. I had to get this thing working last night so I ended up asking my mentor for assistance (he used to work for Sage years ago). He told me he had run into this problem before and ended up just using another preexisting field in the database. We did this last night. The ticket table had a field called USERFIELD8 that we ended up hijacking. This worked.

I would really like to figure out the root cause of this though. I tried doing some reading today, but did not find anything useful.

By the way, we are on version 7.5.0.1484 (LAN). Based on what my colleague has told me, I dont think we can upgrade due to large amounts of customizations.

Anyway, thank you again. If you think of anything please let me know. Take care

Hi Dan

Try this - add another field (a bDummy) to the ticket table - you should then find this activates the other field (if this is the problem I'm thinking of). Let me know how that goes on, otherwise - I can always do a GotoAssist with you to get to the bottom of it.

Regards
Mike

Hi Mike,

I will try to do this later today or tomorrow. I really appreciate your offer on the GotoAssist. I'll post back as soon as I have success or failure

Thank you!

Hi Mike,

I have tried your suggestion and it did not help. Also, I can now reproduce it in our dev environmnet and on a different table (Contact). The fun never ends! Please let me know if you are still willing to do a Gotoassist.

thank you sir!

Sure, go here: https://www.fastsupport.com/826936945 - send me an email when connected (as I'll be back on my iPad!)

ready

Mike,

You rock! Thank you very much for the help and for the work around. I very much appreciate it.

thanks again!

My pleasure, glad we got there! (for anyone else seeing this issue - the issue is secprofile and secprofiledata being truncated - a very old bug. This is fixed in v7.5 Service Pack 2 by running slxsp2conversion.exe - this is the only permanent fix).

I have been experiencing a similar issue but on version 7.2.  There is a custom checkbox on the main account screen which periodically becomes disabled, apparentlty at random, and can only be re-enabled by changing the secrights back to read/write in the admin.

Any advice on how to fix this permenantly would be greatly appreciated.

You can't I'm afraid. Have to suffer the issue unless you upgrade to 7.5.2 at the earliest it was fixed permanently.

Thats unfortnate - thanks for the snappy response Mike.

the old trick of adding ANOTHER field "DummyField" to an FLS  table (Account) should work as a manual, yet permanent, fix as well.

Basically there was a bug in how SLX calculated the triplets needed for storing each fields security profile....3000 fields / 3 = 1000 characters in the Security Profile. 3001/3 = 1000 characters in the Security Profile, you need to add 1 character to store the odd field out......