Digital Workshop

Is there any way of creating a publication level boolean variable? The options seem to be text, number or array...

Thanks,

Melanie

I just use "1" or "0" as a number.

Thanks Swan,

I'll see if I can work with something like you suggest. The trouble is I can't set an initial value of true (or false) to a publication level variable, and I'm using that variable with the button/Checkbox/Linktovariable thingy. This uses a boolean and presumably declares it as a boolean at some point, but because I have only number, text or array to pick, I can't initialise it to true or false.

I know I can use "button is initially down" to set it, to set it to true or false, but I wouldn't expect that to happen until that particular page loads.

This is what I'm proposing to do: I'm getting boolean values from a database and updating these pub level variables (sort of user preferences), so a variable declared as "text" is going to be updated to a bool, is this going to work?

Thanks for your help

Melanie

I think most databases keeps a one byte bool as a 1 or a 0 anyway. I just checked mySQL & Access and they seem to.
In fact all the ASP & PHP code I do for checking the state of a bool is for a 1 or 0 (it works the same as checking for true or false). Although, I'm saying this without first checking it in Opus. I also have never worked a database from Opus either, so I hope I'm not leading U down the garden path.

I'll do a quick test.

Stick with numbers not text.

This worked for both Access (yes/no) bool and mySQL (tinyint).

This is the first time I've played with database on Opus. It's a bit strange to work with. I didn't spend a real lot of time on it but I couldn't see how to select column.record in a multi column recordset.

So Melanie, I trust with this you may be able to thrash it out from here.

Goo Luck ...

Thanks for that, I'm just snooping around the Database stuff at the moment - I'm comfortable with SQL but I'm still learning the script.

Seems that 1 (number) is treated as equivalent to TRUE (bool). Useful to know... I think



I don't understand what you mean here. Normally columns are prefixed by tablename ... for example:

var rset = mydb.ExecuteSQL("select dept.deptno, dept.deptname from dept;")

then to use deptno or deptname: -

rset.FirstRecord();
mydeptnovariable = rset.deptno

kind of thing... Dunno if that helps answer your question...(also hope this is right, I can't open Opus to test it at the moment because of another problem!)

Anyway, thanks for your help and I'll play around with it as soon as Opus is well again.

Cheers Melanie

What you are testing is if FirstRecord() got the first record so even if unit was a string the output would be true. You would only get false if FirstRecord() failed. What you want is

[/code]

Thanks Tony for clarifying everything so elegantly