RJArcher

I'm still going through the Jumpstart process with a Caspio trainer, so I'm definitely NOT an expert, but I developed in Microsoft Access for 25+ years, so I feel your pain. I just got help with a report where I need a number of fields displayed in 3 columns in a List type report and once they got me started, it was pretty easy to "tweak" their solution into what I needed. I'd be happy to share Caspio's solution if it's anything close to what you need. (see attached)

There must be other Caspio developers who, like me, are trying to migrate their apps from Microsoft Access to Caspio. Is there a forum that I haven't found that might contain, tips, tricks and taboos for migrating existing Access apps? Obviously, getting the data across is a piece of cake, but what about recreating complex queries as Caspio Views and things like that?

Problem solved - thank you for your reply and assistance! I'm still struggling with the various syntax schemes as I bounce back and forth between Caspio, JavaScript and T-SQL, but I'm getting there. Thanks again.

I agree! I'm a newbie at Caspio, converting from MS Access, and I find formulas and referencing variables very confusing. Do I use [@field:ItemName] or [@ItemName] or [ItemName] or something else and do I enclose it in single quotes or not? And my current issue is how to include a virtual field on the form in the formula for another field on the same form. The OP is using '[@cbParamVirtual#]' which I've tried, but my understanding is that that notation is for APP parameters. In my case, I'm trying to refer to a simple virtua field defined on the form.