Sholom,

If the control requires the user to download and install a component
then DB will not take on the control. We take pride in the fact that
there are no client downloads needed to develop or run any DB
application. This allows your DB application to be run anywhere in the
world, at any time from any W3C compliant browser. The same applies to
commerical grade applications. These run in IE6 and also require no
client downloads. All you need to run or develop a commercial grade DB
application from anywhere in the world (as long as you have access to
the server) is IE6.

On the other hand if this control is server based and you want to
purchase it, there are ways to use it in DB. The cavat is that it must
run on the server side.

BTW, On-Form Reports were added in the 3.3 release for W3C mode.

Rick

"Rick Weiser" <rickw (AT) designbais (DOT) com> wrote

Oh no- not *another* primitive, limited, restrictive browser-based UI !
And one that Tony likes, pushes and sells.
My God, sirs, have you no shame?

Chandru

ps : in case anyone is humour-impaired, the above is with tongue firmly in
cheek.

[]

I got the humor right off Chandru... Please have a look at this blog
article and you'll see some of the reasons why I support this
particular product.
<http://
removethisNebula-RnD.com/blog/general/
2006/06/the-designbais-audience.html>
(Yes, I need shorter URL's.)

If indeed a VAR or end-user prefers to use the (primitive, limited,
restrictive, LOL) browser-based UI, then I believe this is the finest
product in our market for allowing them to do so. Please note that
I've been supporting DesignBais for over two years and only recently
have many of our colleagues taken a serious look at it, and low and
behold those who have seen it really like it for its intended audience
of developers and end-users. Every week now I'm having lengthy
discussions with companies as we go through the process of figuring
out which MV product will suit their needs the best. In some cases
DesignBais simply isn't the right tool for ... oh sorry ... it simply
doesn't fit. In other cases it's ideal.

Chandru, this software reminds me of a browser version of Forge, as I
remember it. You should have a look just to understand it. I fully
understand you'll have no need for it, but that shouldn't stop you
from making informed comparisons or even recommending it to people who
do fit the profile.

Regards,
T


"murthi" wrote:

Similar to your technique, though no better really, is to have two
On-Form Reports on the same page, and when the user selects a line
item in the first grid you can display the detail (correlated values)
for that line item in the other grid.

The only advantage I see with this is that the first grid doesn't
shift around, and the user can easily click on each master/controlling
element to see detail in the other grid. This is a usability
technique that I read about in some book on the topic recently and it
seems to make sense for some screens regardless of the language or
tools you're using.

HTH
T


"Symeon" wrote:

I'm (obviously!?) no expert in DB, but I would question the need for
multi-value inputs on this sort of device anyway. I know with our RF
warehouse stuff we are happy iof the storeman using them can
(correctly) scan a single item at a time :-)

Also be aware that there may be some "gotcha's" associated with the
browser as well - not all Pocket IE's are equal!

For example, if you are using Telxon units they have an annoying
graphical keyboard that pops up on the screen ... the only "solution"
is to "upgrade" to the Telxon "enhanced" browser, where they have
disabled this (feature?). If you are talking about "real" PDA's, there
tend to be fewer "enhancements" done.


Ross Ferris
Stamina Software
Visage - Better by Design!

Ross, I am sort of in agreement with you due to the space available in
a PDA screen, but we won't gain points in this forum by telling MV
developers they don't need controlling/dependent values, regardless of
the UI.

The MV Input area in DesignBais allows the user to insert, delete,
append related multivalue sets. This is useful for entering multiple
line items of similar structure. For a PDA there could be any number
of applications:
- product ID and QTY during physical inventory
- maybe dinner/beverage selection for restaurant guests
- student name and test scores
- player name, points, and other stats for sporting events
- visitor name and car location for a parking garage
etc...
For some data you wouldn't allow add/delete or even update, but I can
think of a lot of applications where the versatility is beneficial.

T

"Ross Ferris" wrote: