stumped

Try:

let reg := if fasst.Id then "yes" else "no" end

reg

Steven

You need a semi-colon after the end of the if block, since you have another statement following. Actually the semi-colons you use aren't necessary because there are no other commands following in each of the truth or false parts. In this case, however, assigning to a variable is really not needed. If you leave off the variable, it will return yes or no and no semi-colons would be needed.

Peter ...

I'm not saying to use it, use Steven's code, but your code should have looked like this

let reg := "";

if fasst.Id then
reg := "yes"
else
reg := "no"
end;
reg

Regards John

UKenGB - 

Been using Ninox for now nearly 2 years and still on that learning curve !!!.

Ninox catches you out because cos it does some things code wise in odd ways and as the online manuasl is still a few years out of date!

You have to guess at what the improvements/additions/corrections to code lexicon are.

Fortunately, there are some very clever colleagues using this forum who never seem to sleep!

I guess we are all learning together (still!)

You seem to be picking it up much better than I am UKenGB.

Asking a lot of good questions much better phrased than I would have.

I'm essentially coming from a similar place I think, some experience of coding in various languages, previous Database experience, awareness of SQL and basic under the hood stuff and thorough stuck trying to understand the Ninox approach which is different under the hood and keeps a lot hidden to make it more approachable for spreadsheet people.

Documentation is terrible and I find the Nioxus training videos excrusiatingly long winded as they are targeted at thos same kind of basic computer users! If he could just get to the point I could wizz through those 1 hour lessons in 5 minutes! I wish there were a manual and traing more targeted at poeple coming with previous knowledge like us just aimed at explaining the quirks and under the hood stuff that diverges from what we might be used to. Ninox seem powerful and is very affordable but learning it is like fighting through fog and frustratingly feels like it could be so much simpler to learn if it was documented right for us!

All that said, I did learn in the hours of training videos I have suffered through that within Ninox variables only exist for as long as the function they are declared within.

The biggest challenge I'm struggling with right now is fully understanding how selects, paths, and linked tables all work and interact when you call them in code (connecting vs returning arrays vs ???) it all seems a bit mysterious. I wish there was a little variable tracker so you could look at the full contents of a variable and progress line by line through you code watching the value in it change. That a feature I've seen in other devolopment platforms that can be really handy.

Quentin

There is a manual but is it is quite basic (and out of date!) https://ninox.com/en/manual/introduction/basics

I think what you would like to see is a bible or teccy version (so would I :-). There is nothing like reading a large technical manual in bed to keep you awake!

Like you, coming from other vaious software that was well supported document wise it is a learning curve. Especiialy when you are used to defining relationship links by specifying a unique key to foreign keys. etc. Ninox - You link a table and whole table is linked !

All I can say is hang in there - There is some fantastic help to bg had from some very clever people using this (user!) forum and surprisingly - once you stop trying to do things based on what you already know! ie throw it away !- Ninox does become quote clear quickly.

It's actually a great piece of software! far from perfect by anymeans but useful and practical!

Mel