Can't Run WinDataForm Wizard

  • Thread starter Thread starter Mr. B
  • Start date Start date
M

Mr. B

I have VB.net "standard" (2002) and have never been able to run the
WinDataForm Wizard... I ALWAYS get an error message saying that it could not
run the wizard (vsz) file...

The wizard file is located in:
C:\Program Files\Microsoft Visual Studio .NET\Vb7\VBProjectItems

But, the error message shows that its looking in:
C:\Program Files\Microsoft Visual Studio .NET\Vb7\VBProjectItems\Local Project
Items

I've tried copying the file into the "\Local Project Items" folders... but to
no avail.

Anyone know what's going on and how I can fix this?

Much appreciated...

Bruce
 
Bruce,

It certainly should have worked when you added the extra directory, and I
have no idea why you are having problems. Perhaps someone else can help you
there.

I just wanted to point out that the resulting dataform is relatively
useless. If you're having trouble getting started building your own form,
you can post those questions and there are walkthroughs in the help.
 
Kathleen Dollard said:
I just wanted to point out that the resulting dataform is relatively
useless. If you're having trouble getting started building your own form,
you can post those questions and there are walkthroughs in the help.
Click to expand...

Okay...

What I'm trying to figure out is my current application opens an MS Access
file (my first time using ADO). This file has 6 tables. I extract info from
5 of these tables using separate DataAdapter + Datasets..

I do each FILL command one at a time. And there is a 2 second performance hit
on startup of the application (ie: over 15 seconds).

So I'm trying to figure out IF I can somehow open several tables in a "Single"
DataAdapter.

My book on ADO.net (David Sceppa) on Connections walks you through what
appears to be a multiple table connection... but using the Wizard.

So I wanted to see if it would work with my situation.

Regards,

Bruce
(still an ADO newby)
 
Mr. B,

I don't use Access, so I'll have to defer to someone else. In SQL Server, it
would look like

SELECT <fieldList> FROM <Table1>;
SELECT <fieldList> FROM <Table2>;
SELECT <fieldList> FROM <Table3>;
SELECT <fieldList> FROM <Table4>;
SELECT <fieldList> FROM <Table5>
 
Back
Top