Re: Designer
- From: "Ralph" <nt_consulting64@xxxxxxxxx>
- Date: Thu, 15 Sep 2005 18:17:46 -0500
"Graham (UK Beginner)" <nospam@xxxxxxxxxx> wrote in message
news:%236TjabjuFHA.3932@xxxxxxxxxxxxxxxxxxxxxxx
> "Have you been moving things around?"
>
> Everything seems to be in order and in the right place and I still get a
> "class not registered" when I click Add Data Environment on the project
> menu. Could you give me your method of registering components in the
> VB98\Wizards folder so I can compare?
>
> "Your best bet is to use a code only solution using DAO"
>
> I wanted to use a data environment as a "quick fix" solution to create
> reports because I dont know a code solution (DAO). Any pointers in that
> direction would be welcome. I have been introduced to ADO and have it
> on my "do list"
>
> Thanks for the tips
>
The first question...
You open a 'DOS Prompt' and went into the folder and typed...
"regsvr32 msdatobj.dll"
Actually I use one of Randy's tools, and I suggest you try it out.
http://www.usenet-archive.de/comp.lang.basic.misc/85963-Re_registering_or_unregistering_ocx_dll_ax_files_with_a_single_click_.php
A Wild thought - maybe it is related to the menus getting 'disconnected'.
Doubt it, but worth a shot. (It's a good tip to know since you will probably
need it some do to fix some other 'menu' problem. <g>)
http://support.microsoft.com/kb/266747/en-us
The second question... "using a code only solution" should really be
directed to Veign.
The DataEnvironment generally gets a 'bad' review from many VBers.
Especially 'advanced' programmers. As for me, I'm just sort of
run-of-the-mill and have no problem with DE. As long as you realize what it
is - a class library lying on top of ADO with a visual component (the
designer).
In my experience it is a great learning tool and good environment to rapidly
develop ad hoc client-server apps. I like the learning aspects of it,
because it gives a visual representation of the ADO class library. You get a
connection builder and tester, SQL builder, procedure builder, you can set
recordset attributes from a dialog, a simple report writer, etc. It also
catches ADO errors/events.
I like the rapid development part because building a client-server app often
means chewing on a whole host of issues, and most of the data-issues boil
down to typing the same stuff over and over. and when you are new you tend
to forget something. You can waste a lot of time on trees and miss the
forest.
Also I like the fact that developers exposed to the DE and then go on to a
more 'code-only' solution, bring with them a better mental model of how to
go about designing a client-server app. Many programmers who start out with
"code-only" never discover the advantages of canned procedures,
parameterized queries, or ADO events, until much later.
It's principle disadvantage and advantage is it uses "data binding". Data
binding (or rather Data Awareness) is unfortunately a double-edged sword -
it provides a quick 'n dirty way to 'attach' data to controls. But by making
it simple, a lot of control is taken away. The other edge is a rather
sophisticated method of providing your own Data Binding - but that leads to
a subject that is poorly documented. And can carry a performance penalty in
a large commercial type project.
IMHO I believe being expose to Data Aware technology is useful. (It is what
ADO.NET is all about), as once again it teaches good OO skills. "Code-only"
approaches without discipline invariably become procedural in nature.
Others of course disagree. <g>
-ralph
.
- Follow-Ups:
- Re: Designer
- From: UK Beginner
- Re: Designer
- From: UK Beginner
- Re: Designer
- References:
- Re: Designer
- From: Ralph
- Re: Designer
- From: UK Beginner
- Re: Designer
- Prev by Date: Re: Font looks fine in 3rd party app, but looks tish in VB6 [Multiposted]
- Next by Date: Re: Using early-bound interface on a late-bound object
- Previous by thread: Re: Designer
- Next by thread: Re: Designer
- Index(es):
Relevant Pages
|
Loading