#Superbase!
8 messages in this thread
A ran into a couple of gotcha's in SuperBase.
Perhaps you folks have work-arounds? Here are the problems.
I created a form and filled it with variables using the CLC button. I did
this so I could have control of the data that appeared on the screen. I
created four pages of screens. On the fourth page, I entered a new
variable, made it a transaction line, and saved my form. I then opened it
with a DML program. All of the variable and such work, except for the
transaction lines on the last page. Yes, I know how to do them and the
other transaction lines worked. I copied page 4 into a new form and made
it page 1. Guess what? It works. Is there a variable limit to a single
form? Since there were a lot of transaction lines on the prior pages I
had nearly 200+ variables when I printed them with the '? memory' command.
I did try using a different variable name, etc. Nothing worked until I
moved page 4 into a form by itself.
The next problem came when I tried to go back from this new form to the
old form. I discovered that SuperBase will wipe out any transaction line
variable (remember I am using CLC to create these transaction lines,
instead of using a real database field), the variable was there, but the
contents were not. Interestingly enough, the non-dimensioned variables on
that form were not wiped out.
Another interesting thing the forms editor will allow you to do that is
not supported is taking a checkbox gadget and make it a transaction line.
I would think it would work, the forms editor thinks it should work, but
DML never picks up the clicked value in an array.
Finally, I called Oxxi today. Oxxi only provides three, count 'em three
hours a day for support. Now I hardly ever call for support, but when I
do expect there to be someone there to be able to answer my questions and
secondly require reasonable support hours. I realize that Oxxi is not
that big of a company but it seems to me if they can afford to buy
SuperBase they could afford a least one person to do support for 8 hours a
<continued>
I had a similar problem with the push-buttons that you had with the
check-boxes. The form-designer doesn't seem to mind it but as soon as you
try it the value disappears. For now my solution is to create a seperate
CMD button for each transaction and have it do a 'SELECT FORM ROW #"
command where '#' equals whatever transaction the button applies to (I set
the 'push button' and 'skip entry execution' features also). You can then
enter the commands that you wish to occur (after the SELECT FORM ROW).
I also have to other buttons to scroll through the transaction pages..
It'd be nice of Sbase allowed a line by line scroll.
As for the transaction problem on page 4, the only thing I can think of is
making sure your in the right page with 'FORM 4'. I had the impression
from using the form's designer that it will let you have seperate
transactions as long as they are on seperate pages. Guess I'll have to
re-examine that assumption.
I hope everything works out and if you think Sbase can be a pain in the
neck sometimes, join the crowd. It takes practice, patience, and more
practice to get the hang of this thing.
Shannon
I appreciate your reply.
Are you saying there is a limit of one set of transaction lines per form?
Hmmm…
-mark=
Mark,
SBase allows only one set of transaction lines per form. Want more lines,
gotta use a different form. It causes all sorts of problems otherwise.
Actually, this is sort of good. Large multi-paged forms take up much more
RAM than multiple form files that are loaded on demand. OTOH, this causes
delays.
Transactions are powerful bt have some quirks that make me want to bang my
head against the keyboard!
-Chas
Mark…
The manual states that (in the transaction chapter) but the form designer
gave me impressions otherwise.
Havn't really tried it yet. .
Here we go, page 4-1 "You may only create on block of transaction
lines on a form." I did a quick test (tried creating a transaction
on a seperate page) and it seemed to have no Qualms about it.
But I never tested the form to see how it REALLY reacts.
Shannon
Shannon,
The problem only appeared after I had added quite a few variables to the
form. I had 4 pages of them. They numbered greater than 255. I suspect
that I ran into a variable limit for a form.
I coded around it… I took page 4 and made it page 1 of another form and
hung onto all of my data.
-mark=
Mark,
only one set of transaction lines per form. If you are willing to hack
around, I may send out my scrolling transaction line solution for
SUperbase. it takes a few global variables and about 80 lines of code.
Ciao, Neil
Only one set of transactions lines per form eh? That is in the manual, I
just found it. I wonder why there is such a limitation?
Neil, I would love any code that you might wish to share!
-mark=