DevWizard 2001 Final Release!! For VB, ASP, COM, and SQL Developers

[Dave V]

We are pleased to announce the Final Release of DevWizard 2001
Version 2.0. DevWizard 2001 is a VB6 AddIn which allows
a developer to create an entire 3-tier application with just a few
clicks of his or her mouse. All you need to do is supply a valid
ODBC or OLEDB data source, and DevWizard 2001 does the rest.

Key features include:

- Automatic generation of XML-enabled COM/COM+ objects
- Automatic generation of ANSI SQL stored procedures
- Automatic generation of ASP pages with JavaScript client-side code,
useable with any browser
- Optional generation of XML-enabled stored procedures for use with
SQL Server 2000 (or later)

Just visit our web site at http://www.q-d.com for your free evaluation
copy. While you're there, feel free to join our discussion group to
share your opinion with us and the rest of our growing user base.

--

Thanks,
Dave Verschleiser
Q&D Software Development
http://www.q-d.com
********************************************************************
Creators of DevWizard 2001, WebForms, and WebMania!
********************************************************************

[the4man]

There is not support for ObjectContext

They use global variables in .BAS modules

They use properties instead parameters, so if you want to install the
objects created with this tool in MTS/COM+, or simply make good use of the
distributed transactions (that means that you must to call
SetComplete/SetAbort), you will have to do many changes in the code.

[Dave V]

Hi,

Thanks for showing interest in DevWizard 2001. I'd like to address your
concerns:

To answer your second concern, the only global variable generated by
DevWizard 2001 is to store the connection string. (The connection objects
themselves are not global.) Storing a connection string as a global
variable is common practice. Otherwise, should your connection string need
to change, you'd have to change it everywhere in your code. If you are
uncomfortable with this global variable, you can of course modify the code
as you see fit.

As for your other two concerns, if you're using COM+ under Windows 2000,
there is no need to explicitly create ObjectContext, as COM+ handles context
for you automatically. You simply need to change the MTSTransactionMode
property to something other than 0; whichever value happens to be
appropriate in your circumstance. If you're not using COM+ under Windows
2000 (either you're running NT4 or using MTS), it's a matter of a few lines
of code to create and then close your context.

Please keep in mind that DevWizard 2001 is meant to assist you in your
coding, which it does tremendously, as evidenced by the overwhelming
response we've had since its final release just 3 days ago (and in beta
before that). As advertised, DevWizard 2001 can save you tons of time by
generating COM/COM+ objects, stored procedures, and ASP code in a matter of
seconds, based only on an ODBC or OLEDB provider that you indicate.
However, you will undoubtedly have to modify any generated code to suit your
particular needs.
There is no tool anywhere (including DevWizard 2001) that will generate
an entire application for you which you can take to your users as a finished
product without at least some amount of modification on your part. That
being said, having spent many years in many different corporate development
environments (both as a consultant and an employee) I can say without
hesitation that DevWizard 2001 comes closer to that goal than any other
product I have ever seen. In fact, although you may not be able to present
the DevWizard-generated code as a production application, it is entirely
possible that it can serve as a perfectly good working prototype for your
application (including front-end, middle-tier, and stored procedures). I
know this for a fact, because I have delivered project prototypes myself
using the code that went into the making of DevWizard 2001, all of which met
with user and managerial approval.

What's more, the code that DevWizard 2001 generates is clear, concise,
and well documented, with module and function headers which explain the
purpose of each respective module/function. Because of this, any changes
you wish to make (assuming a fair understanding of the technology involved)
should require very little time and effort. Much less time and effort than
it would take to create an entire multi-tier application unassisted.

Thanks,
Dave Verschleiser
Q&D Software Development
http://www.q-d.com

"the4man" <no...@pongo.es> wrote in message
news:3ae67d2c$1...@news.arrakis.es...

[the4man]

First, Thanks for your reply!

"Dave V" <d_ve...@hotmail.com> escribió en el mensaje
news:7ggG6.2305$Yo.7...@typhoon2.ba-dsg.net...
> Hi,

>
> To answer your second concern, the only global variable generated by
> DevWizard 2001 is to store the connection string. (The connection objects
> themselves are not global.) Storing a connection string as a global
> variable is common practice. Otherwise, should your connection string
need
> to change, you'd have to change it everywhere in your code. If you are
> uncomfortable with this global variable, you can of course modify the code
> as you see fit.

The problem is not to store data in global variables. The problem is to
store it in a .BAS module. First, only the objects that lives in the same
STA can share this variables. Second, global variables are stored internaly
in the TLS, so i think that it makes impossible to create poolable objects
(neither in VB7)

Some recomendations:

Add an option that permits to select the TransactionMode property, and
always add code for ObjectContext object (is a good programming tecnique
although it isn't necessary).

Add an option that permits to select between properties or method's
parameters. This is very important, because is necessary to create stateless
objects if we want to make good use of all the advantages of MTS/COM+.
There is only one case where the properties are a good idea: when the
objects doesn't use transacctions neither just-in-time activation. This is a
rare case, because then we are not using any advantages of MTS/COM+ !!!. At
present, the code generated by DevWizard needs many modifications. Isn't
enough with to change the MtsTransactionMode to another value.

Add an option to generate de ASP pages in JScript instead of VBScript.
JScript has a powerful mechanism of error handling: try/catch/finally
statment.