Example needed

I've lost my way a bit.

function main()
   wxwindow w
   dataform1 f
   wxmenubar mb
   integer e, width, height, dispwidth, dispheight
   string filename, cd, result, errtext

   e = 0
   cd = getcurrentdirectory()
   //  To "Load" A Specific form in .sxf format.
   filename = "C:\Program
Files\SIMPOL\Utilities\desktop\EnterEmp.sxf"
   //  To "load" a user chosen form .sxf format.
   //result = ""
   //wxfiledialog(.nul, "Pick a form to show", cd, "",
"*.sxf", 
"open,mustexist", filename, result)
   //if result == "ok"
   errtext = ""
     f =@ opendataform1(filename, error=e, errortext=errtext)

ETC.  ******************

But how would I call a function to create the dataform1

I was thinking instead of f =@ opendatafrom1(etc) line,
I'd put

f =@ makeform(f)

and then I'd have

function makeform(dataform1 f)
//in here I put in the stuff that is generated when you save
//as dataform1 program in Desktop
//BUT THIS DOESN'T SEEM TO WORK.
end function f

But I get build error for every single dataform1text control.

E.g.

Error in statement: fc =@ f.addcontrol(dataform1text, 174, 106, 96, 19, 
text="SSN", alignment="left", name="text18"",
page=page, error=e)"
Error: Unexpected end of statement.

Aha

This is the problem:
name="text20""

should be
name="text20"

Ok, so it compiles, but here is where I get error 21:

dtable =@ f.addtable(table, src, error=e)

is "dtable" supposed to be "datatable" as in

dataform1table datatable

but then I get lost when I get here

table =@ csrc.table

****

Perhaps I should ask a different way.  Has anybody been able to use the
the sma generated by the Desktop's save as dataform1 option AS IS?

I am guessing by lack of reply that no one has really been able to use
the dataform program generated by form designer in the Desktop, "as
is".

I suppose eventually one might figure out as I did the bug that produces:

name="text18"",

instead of

name="text18",

for dataform1text.

But the whole confusion about

dtable =@ f.addtable(table, src, error=e)

remains a confusion at least to me.

JDK


Kromkowski wrote:
> I've lost my way a bit.
> 
> function main()
>   wxwindow w
>   dataform1 f
>   wxmenubar mb
>   integer e, width, height, dispwidth, dispheight
>   string filename, cd, result, errtext
> 
>   e = 0
>   cd = getcurrentdirectory()
>   //  To "Load" A Specific form in .sxf format.
>   filename = "C:\Program
Files\SIMPOL\Utilities\desktop\EnterEmp.sxf"
>   //  To "load" a user chosen form .sxf format.
>   //result = ""
>   //wxfiledialog(.nul, "Pick a form to show", cd, "",
"*.sxf", 
> "open,mustexist", filename, result)
>   //if result == "ok"
>   errtext = ""
>     f =@ opendataform1(filename, error=e, errortext=errtext)
> 
> ETC.  ******************
> 
> But how would I call a function to create the dataform1
> 
> I was thinking instead of f =@ opendatafrom1(etc) line,
> I'd put
> 
> f =@ makeform(f)
> 
> and then I'd have
> 
> function makeform(dataform1 f)
> //in here I put in the stuff that is generated when you save
> //as dataform1 program in Desktop
> //BUT THIS DOESN'T SEEM TO WORK.
> end function f
> 
> But I get build error for every single dataform1text control.
> 
> E.g.
> 
> Error in statement: fc =@ f.addcontrol(dataform1text, 174, 106, 96, 19, 
> text="SSN", alignment="left",
name="text18"", page=page, error=e)"
> Error: Unexpected end of statement.
> 
> Aha
> 
> This is the problem:
> name="text20""
> 
> should be
> name="text20"
> 
> Ok, so it compiles, but here is where I get error 21:
> 
> dtable =@ f.addtable(table, src, error=e)
> 
> is "dtable" supposed to be "datatable" as in
> 
> dataform1table datatable
> 
> but then I get lost when I get here
> 
> table =@ csrc.table
> 
> ****
> 
> Perhaps I should ask a different way.  Has anybody been able to use the
> the sma generated by the Desktop's save as dataform1 option AS IS?
> 
> 
> 
> 
> 

Kromkowski wrote:
> I am guessing by lack of reply that no one has really been able to use
> the dataform program generated by form designer in the Desktop, "as
is".
> 
> I suppose eventually one might figure out as I did the bug that produces:
> 
> name="text18"",
> 
> instead of
> 
> name="text18",
> 
> for dataform1text.
> 
> But the whole confusion about
> 
> dtable =@ f.addtable(table, src, error=e)
> 
> remains a confusion at least to me.

I will have a close look in the near future, prior to releasing the next
release. I have been a bit on the busy side of late.

John Roberts wrote:
> "Kromkowski" <kromkowski@verizon.net> wrote in message 
> news:ff0jpu$var$1@ipx22096.ipxserver.de...
>> I am guessing by lack of reply that no one has really been able to use
>> the dataform program generated by form designer in the Desktop,
"as is".
>> I suppose eventually one might figure out as I did the bug that
produces:
>> name="text18"",
>> instead of
>> name="text18",
>> for dataform1text.
> 
> Well spotted.
> 
>> But the whole confusion about
>> dtable =@ f.addtable(table, src, error=e)
>> remains a confusion at least to me.
>>> is "dtable" supposed to be "datatable" as in
>>> dataform1table datatable
> 
> If you look at the list of declared variables "dtable" is not
listed and 
> this must be a bug in the form code generator. Hence the error 21
"object 
> not found".

Yeah, I saw that.  That is why I asked whether "dtable" was supposed
to 
be "datatable" which was declared.

> 
>>> but then I get lost when I get here
>>> table =@ csrc.table
> 
> csrc is a type created for the dataform setup and declared in the line
> dataform1controlsource csrc
> If you add the lib\formlib to your project you will be able to see type 
> dataform1controlsource in the list of types from that lib in the type view

> in the the ide. Note that one of its properties is "table". It
will refer to 
> either .nul or a data table.
> 
> The variable "table" (not csrc property "table") is
declared in this line as 
> a type just like "type(wxformcontrol) fc" is in a form build
prog.
> type(db1table) table
> hence we can do "table =@ csrc.table"

Ok.  But I have a better understanding.  I'll go back and look again.

> 
>>> Perhaps I should ask a different way.  Has anybody been able to use
the
>>> the sma generated by the Desktop's save as dataform1 option AS IS?
> 
> I haven't really played with this much as I have had many other things on
my 
> plate and dataforms have been and are unfinished. I have tended to 
> concentrate on things that worked and build libraries for other components

> ready for when all this did work. I have mainly looked as it developed and

> you may notice none of the dataform stuff is in the conversion prog 
> sbl2simpol, mainly because there was not enough of it finished and I had 
> other things to do. In SB, dataform management is not exposed to the user
as 
> much as it is in simpol.
> 
> Dataforms are work in progress and glitches are expected in this scenario.

> Imagine trying to write and debug a very large prog that is written in a
new 
> language with new facilities being added to it as you go along with some 
> still absent. Add to that, no forum you can fall back on with questions,
you 
> must attend to other problems rearing their heads frequently as well as try

> and explain things here. As such I don't expect it to work smoothly yet and

> am happy to objectively (usually) report things like double quotes or 
> missing variables and go on working with something else. Those sort of 
> reports are very useful when developing something. I guess it is all a 
> matter of expectations. If you labour under the idea that it is a finished

> product then you will get confused and frustrated and maybe express that.
My 
> expectations are high for the finished product but low for the pre-release

> product. That is what being a pre-release tester is all about. The plus
side 
> is that you have a head start on learning how it all works. Sorry to go 
> on...
> Cheers, John


Look. I know that nobody wants to say anything bad.  But, come on.  I 
got my chops busted for saying a year ago that what was being released 
then really wasn't a beta product at all but an alpha product.

And Simpol put out a Press Release in February/March 2007  saying that 
the release date was April 2, 2007.

In spring of 2006 the US rep tried tell me a release date was 
unequivocally going to be by the end of 2006.

If people admit things are alphas and don't purport to announce 
obviously unmeetable dates, then there is no problem.  Because everybody 
knows what they are getting.

I don't labor under the idea that it is a finished product because it 
obviously isn't.

The is a massive difference between being a pre-release beta tester and 
a pre-release alpha tester.

In October 2005, this was alleged:

"Superbase is now working with several of its customers to actively 
convert their applications to Superbase Next Generation."

And Superbase had the balls, in 2006, to suggest that they'd convert on 
of my application to Simpol/SBNG for $60,000.  How possible could they 
possibly do that when the was no Simpol/SBNG sufficiently developed. It 
was also a ridiculous estimate.

While the product is definitely real now, there was a lot of vaper, 
hype, and illusion in the past.  Remember Simpol as a project has been 
around since what 1999!  That SB2 was ten years in the making with a big 
team, is really irrelevant.

The ostensible rationale is to deal with VISTA, but they've admitted 
that there not even testing on VISTA.

"Kromkowski" <kromkowski@verizon.net> wrote in message 
news:ff0jpu$var$1@ipx22096.ipxserver.de...
>I am guessing by lack of reply that no one has really been able to use
> the dataform program generated by form designer in the Desktop, "as
is".
> I suppose eventually one might figure out as I did the bug that produces:
> name="text18"",
> instead of
> name="text18",
> for dataform1text.

Well spotted.

> But the whole confusion about
> dtable =@ f.addtable(table, src, error=e)
> remains a confusion at least to me.
>> is "dtable" supposed to be "datatable" as in
>> dataform1table datatable

If you look at the list of declared variables "dtable" is not listed
and 
this must be a bug in the form code generator. Hence the error 21 "object 
not found".

>> but then I get lost when I get here
>> table =@ csrc.table

csrc is a type created for the dataform setup and declared in the line
dataform1controlsource csrc
If you add the lib\formlib to your project you will be able to see type 
dataform1controlsource in the list of types from that lib in the type view 
in the the ide. Note that one of its properties is "table". It will
refer to 
either .nul or a data table.

The variable "table" (not csrc property "table") is declared
in this line as 
a type just like "type(wxformcontrol) fc" is in a form build prog.
type(db1table) table
hence we can do "table =@ csrc.table"

>> Perhaps I should ask a different way.  Has anybody been able to use
the
>> the sma generated by the Desktop's save as dataform1 option AS IS?

I haven't really played with this much as I have had many other things on my 
plate and dataforms have been and are unfinished. I have tended to 
concentrate on things that worked and build libraries for other components 
ready for when all this did work. I have mainly looked as it developed and 
you may notice none of the dataform stuff is in the conversion prog 
sbl2simpol, mainly because there was not enough of it finished and I had 
other things to do. In SB, dataform management is not exposed to the user as 
much as it is in simpol.

Dataforms are work in progress and glitches are expected in this scenario. 
Imagine trying to write and debug a very large prog that is written in a new 
language with new facilities being added to it as you go along with some 
still absent. Add to that, no forum you can fall back on with questions, you 
must attend to other problems rearing their heads frequently as well as try 
and explain things here. As such I don't expect it to work smoothly yet and 
am happy to objectively (usually) report things like double quotes or 
missing variables and go on working with something else. Those sort of 
reports are very useful when developing something. I guess it is all a 
matter of expectations. If you labour under the idea that it is a finished 
product then you will get confused and frustrated and maybe express that. My 
expectations are high for the finished product but low for the pre-release 
product. That is what being a pre-release tester is all about. The plus side 
is that you have a head start on learning how it all works. Sorry to go 
on...
Cheers, John