Currently this is true (only IIS on Windows). We are actively
investigating porting the product to Apache on Linux. Expect some news
within a few weeks.

Dave

frosty wrote:

You were right but you are no longer so. There is now a more
traditional way of pricing which provides an upfront fee, an annual
maintenance fee and a perpetual license. See your DesignBais
representative (that would be me) for details. Dave@designbaisDotCom



Dave

Great. Then I'll give the product another look. I recall being impressed
with Tony's Demo at the CDBMA meeting. But the pricing sounded too much
like a Raining Data idea.

Mark Brown

"DaveinBoston" <dave (AT) subanplace (DOT) com> wrote

I have heard of DesignBais, and it sounds great (though I've not looked at
licencing).

I'm wayyyy to far down the line with .net client-server application to
consider jumping ship.

However, with .net 2005 and one-click technology actually starting to look
promising, then I guess I'm closer to something that deploys via a browser..
For my main application (which is never going to have any "public"
interfaces) this will be fine. For publically available interfaces, I
still have vb.net running within aspx against the same back end to fall back
on...

As it stands, my apps are pretty much drag and drop screen designs calling
databasic back end business logic. A simple data-entry form can be written
with about 3 or 4 lines of code (to read and write the record) - the rest
being databound widgets....

I know I don't have the generically perfect solution, but it's perfect for
me... My client deployment cost is zero, and I can run with a low ratio of
jBase server licences (1:10 or less though if I was less than honest I could
get away with a single jBase enterprise licence as all database access
appears to come from the sever due to the way I've implemented the message
queuing!!) to client users - I use message queuing technology to pipeline to
the database...

Regards
Simon


"DaveinBoston" <dave (AT) subanplace (DOT) com> wrote

Simon, I've mentioned some of these things before but this is a good
time to refresh the discussion. Note that I've been an open fan of
DesignBais now for well over a year.:

DesignBais is a great product and perfectly suited to the Pick
developer who doesn't know or care about .NET, ODBC, sockets, ActiveX,
Perl, or any of these other tools that we discuss in these forums.
DesignBais is not for us, it's for your meat and potatoes Pick BASIC
developer that wants a great web interface without the complications
of the web getting in the way.

You mention that you can do everything you need for free. That's
because you've done your homework in the school of hard knocks to get
things working the way you want. DesignBais, like many tools in our
market, is a "convenience" tool, which has a fee for those who choose
not to do all the research or hire someone else to do the coding.

But there are a lot of other advantages. It's a "buck stops here"
kind of product. The MV developer only needs this product with the
MVDBMS and BASIC, nothing else. There's no concern about training
people into Pick or .NET, or losing well trained people. There's no
need to keep up with cross-browser HTML or scripting issues. And
because the source company is so responsive there's no vulnerability
that there is something wrong with the software that will never get
fixed.

From a political standpoint we see it's also a good business buy: The
company has hired Dave Bryant and others specifically to take the
company to "the next level". They were able to do this based on many
successful sales over the last year - for any nay-sayers, consider the
number of companies that have already gone through the sales cycle
with this product, compared it to competing products, and made their
decision in favor of this product. That's a lot of precedent that
makes it a safe bet that all the questions have been asked and
reasonably answered. And hey, Dave isn't cheap and I don't rave about
products for no reason - that's gotta tell you the software is not
only technicall good, but it's selling well too.

Back to the idea that DesignBais isn't for "us". In a way it is. I
sell solutions to VARs and end-users. My set of solutions needs to
include products that will make these clients independent of me for
perpetual services. My idea of a happy client is one that has paid me
for something once and they don't "need" me for that same thing later.
For some of these clients, DesignBais is ideal because I can develop a
solution, pass it to the VAR/end-user developers, and from then on
they can maintain it on their own without calling me or taking a class
in .NET or some other technology. So DesignBais is a real "solution",
not just an answer to a client problem that's convenient for me - big
difference there. If a client says they want .NET or FlashCONNECT and
and they want to maintain the code, then that's what they get, but if
a VAR's knowledge is limited to spelling HTML properly then I'd prefer
to lead with DesignBais.

HTH.
Tony

TG@ removethisNebula-RnD
..com

Feel free contact me for related product and services.
Yes, this is a solicitation, but perfectly in context


"Simon Verona" <news (AT) aphroditeuk (DOT) com> wrote:

Tony

All comments accepted and agreed....

As you say I probably wouldn't have chosen DesignBais - my long term aim is
to become less dependent on multi-value. I've been through the pain and
spent the development bucks getting my own development platform working, so
I guess it's time to reap the benefits in terms of reduced cost of
deployment! If I was so minded, I could probably package up my development
code into a product similar to mv.net (which it is probably very similar
to!).

The tools available have matured significantly over the past 2-3 years
(products like DesignBais, mv.net and all) and they should all be seriously
considered - they all have pro's and cons which need to be weighed up

One area that I feel that i am perhaps "above the curve" on is in
interaction with other products/technologies. Microsofts dotnet is a superb
development platform to integrate with anything. It's "mainstream", can do
anything, it's all been done before and is well documented... You can
leverage easily both from your own code and the code of others (I loose
track of the no of times that I've inherited from third party controls and
tweaked them for my own use - for example, the reporting control that I
adapted to take a databasic subroutine name as a parameter which then called
that databasic subroutine taking the returned data and converting it into
it's own internal format...).

I'm also one of those people who don't like to make compromises. I would
prefer to, and enjoy spending a little time developing something that fully
fits my needs. I like to know how things work! Whilst the original
development of the platform took a little time (read weeks not years here),
there has been a continual investment in the development platform as I go
along to improve it.

Taking another example - a couple of weeks ago, I decided that it would be
great to change the design of all user interface widgets (textboxes,
drop-downs, radio buttons etc) so that they turned yellow when "active", I
also wanted to change the way that non-updateable text boxes displayed so
that it was clearer that they couldn't be updated.

I just went back to my original .net classes for these widgets (which in
turn are inherited straight from the standard Microsoft ones) and changed
the code to do this... Hey presto, an instant change right through my app -
this is object orientation at work!!! I feel more in control of my own
destiny...

Using dotnot also means that I can employ developers "off the street" -
dotnet programmers are much more readily available than multi-value ones.

Anyways, whilst I'm not saying that the path I've taken is for all, and I
know that I have set myself in a certain direction that has perhaps closed
certain future paths for me, I'm happy... and that's what counts

Regards
Simon


"Tony Gravagno" <g6q3x9lu53001 (AT) sneakemail (DOT) com.invalid> wrote

Tony,

I have never been referred to as an other, but, coming from you its a
compliment ;-).

Let me say this though, expect big things from DesignBais in coming
days, weeks, months, etc.

Rick Weiser
DesignBais International
rick (AT) designbais (DOT) com