Frank,

I note there is filter by control on the list, which as you may recall
one of my long time favorites.

Any chance this may get implemented by referring to the control in the
sql string, i.e. MSA style: where column = [control1]? And then use
prepared queries updated like the master-slave linked fields?

Although I tried quite hard in the past and even dove into your sources
to figure out how to do this in Basic, I never managed.

At the time it appeared that you need to have analyse queries on to get
parameters to work.

I found where to store the data for the parameters, and was not able to
fill them with data. But not without the dialog box popping up after
requery which destroys the data just stored. Actually this dialog box
needs to be made aware not ask the user for values that had just been
set by macro code.

And disabling analyse queries disabled parameters all together.

Anything I can do to help?

Ferry

Op donderdag 22-01-2009 om 12:18 uur [tijdzone +0100], schreef Frank
Schönheit - Sun Microsystems Germany:

> Hi Oliver,
> 
> > * A Tab control for forms (and dialogs).
> 
> noted
> 
> > * Linked tables from different DBs.
> 
> already existent in the feature pool :)
> 
> > * SRB should be the standard report engine.
> 
> noted
> 
> > * Native support not only for MySql but also for PostgreSql, SQLite3 and 
> > perhaps for Firebird.
> 
> noted
> 
> > * The current implementation of Base's forms just seems to put Writer 
> > forms into a new (as of OO2) container format which is quirky and 
> > limiting. Are there any plans to implement true, native DB forms instead 
> > of abusing Writer's/Calc's old (OO1.x) functionality?
> 
> This item exists as "dialog-based forms. coincidentally, this is one of
> my personal favourites ...
> 
> > * A runtime engine for Base applications
> 
> noted
> 
> > * More speed for record operations / navigation (also already mentioned 
> > here).
> 
> noted
> 
> Thanks & Ciao
> Frank

Reply via email to