Search results

Dan, has this feature gotten anywhere? Or have you all published any "best practices" for working with large forms?

Phil, I'm just seeing this now as I come back to see if this functionality has been developed over the last three years. It appears that it has not. I am not a developer, though I think I could still assist. Love that your code is looking for inconsistencies in your form logic!!! Are you...

And when I closed and reopened, all of the fields (90 of them) are there in field settings but the form is gone (all 90 had been configured) and wants me to start over. The form for the 90 fields looked like 5 pages of this so the most tedious, but not the fastest, form to setup...

It has happened again...AGAIN on a HUGE form I've been working on for hours. I'm not sure what created this JIT Exception this time. I do know that I used 'undo' but never to get back the whole form that I accidentally erased as last time. From what I can remember it was just to undo random...

Does anyone know if there is a way to change the settings of multiple fields at the same time? For instance, if I've added a bunch of fields and they've defaulted to FieldType: Text, but I would like to change them all to Checkbox AND Show in Grid is there anyway to select them all and make...

Does form logic override what is setup in the field settings? I have four fields in a session set to enable lookups on another session. I also have ExecuteSQLs in the form logic to do the same...I cannot get the fields to actually lookup consistently. I've tried: 1) enable lookups in field...

It can be duplicated by having a form with many fields (on and off the visual page for the device), delete the whole form, then hit undo. The error comes up when you deploy.

I agree. I've been trying to modify a program that Joe (JK) built and his form logic has a bunch of AfterScan events setup on a checkbox field, which doesn't make sense to me for the reason you just mentioned. "skipped altogether" was meaning what you said...that for it to be effective it...

Anyone know what an Afterscan event (used in the logic) on a checkbox would mean? What specifically triggers it if a checkbox could be skipped altogether?

I've gotten this strange error twice while tweaking a pretty robust form. Each time I lose all of my work and have to painstaking start over. Has anyone experienced this? The second time it happened I think I figured out that it happened after I accidentally erased the whole form and then...

It would be nice to be able to use Markup to format ConfirmationPrompt messages and other popups...at least to create line breaks.

It would be great to be able to pull a program off of a Mobile Device and into TPDesktop.

It would be nice to be able to export or at least view on screen a current "dictionary" or key of all the Control IDs in use on a form. It would make building logic for forms significantly easier if you didn't have to constantly search for Control IDs controlling your different fields as well...