|
 |
aspx_beginners thread: Binding to a database
Message #1 by ejacobse@a... on Wed, 19 Sep 2001 19:38:03
|
|
I am trying to connect to either grocertogo.mdb or northwind.mdb to get my
feet wet. I have successfully run other ASPX pages but I haven't been
able to connect to a database. I get:
Connection failed to open.
System.Data.OleDb.OleDbException: No error information available:
0x800401F9. at System.Data.OleDb.OleDbConnection.ProcessResults(Int32 hr)
at System.Data.OleDb.OleDbConnection.CreateProvider() at
System.Data.OleDb.OleDbConnection.Open() at
ASP.oledb_connection_aspx.Page_Load()
This was the result trying to run the first example in the book "Beginning
ASP.NET using VB.NET"=oledb_connection.aspx.
Any ideas anyone?
Message #2 by "John Godfrey" <jogod@b...> on Wed, 19 Sep 2001 20:18:00 +0100
|
|
Hi,
Don't know what's causing the problem from the message, but I hope this
helps out.
I've downloaded the code and tested it on my system and it works fine,
although I haven't checked the downloadable code against the book
contents. What version of vs.net are you running? The easiest way to
check that your system is working ok, providing you are running vs.net
of course, is to do the following:
1) Create a new vb web app
2) Drag a new oledbconnection object from the toolbox onto webform1.aspx
2) Click the connectionstring property and create a new oledb jet4.0
connection and choose your access database
3)Drag an oledbdataAdapter onto the form and use the exsiting
connectionString and generate a simple query
4) Click on generate preview in the properties box and in the resulting
dialog click fill dataset.
If this generates data then you know that your environment works OK and
you can check the resulting code to enable you to figure out what's gone
wrong with yours. If it is down to the code in the book being incorrect
then please let me know.
Thanks
John...
-----Original Message-----
From: ejacobse@a... [mailto:ejacobse@a...]
Sent: 19 September 2001 19:38
To: aspx_beginners
Subject: [aspx_beginners] Binding to a database
I am trying to connect to either grocertogo.mdb or northwind.mdb to get
my
feet wet. I have successfully run other ASPX pages but I haven't been
able to connect to a database. I get:
Connection failed to open.
System.Data.OleDb.OleDbException: No error information available:
0x800401F9. at System.Data.OleDb.OleDbConnection.ProcessResults(Int32
hr)
at System.Data.OleDb.OleDbConnection.CreateProvider() at
System.Data.OleDb.OleDbConnection.Open() at
ASP.oledb_connection_aspx.Page_Load()
This was the result trying to run the first example in the book
"Beginning
ASP.NET using VB.NET"=oledb_connection.aspx.
Any ideas anyone?
$subst('Email.Unsub')
Message #3 by ejacobse@a... on Wed, 19 Sep 2001 20:08:46
|
|
> I am trying to connect to either grocertogo.mdb or northwind.mdb to get
my
> feet wet. I have successfully run other ASPX pages but I haven't been
> able to connect to a database. I get:
>
> Connection failed to open.
>
> System.Data.OleDb.OleDbException: No error information available:
> 0x800401F9. at System.Data.OleDb.OleDbConnection.ProcessResults(Int32
hr)
> at System.Data.OleDb.OleDbConnection.CreateProvider() at
> System.Data.OleDb.OleDbConnection.Open() at
> ASP.oledb_connection_aspx.Page_Load()
>
> This was the result trying to run the first example in the
book "Beginning
> ASP.NET using VB.NET"=oledb_connection.aspx.
>
> Any ideas anyone?
By the way, this was the first example in CHAPTER 12.
Message #4 by ejacobse@a... on Thu, 20 Sep 2001 00:42:50
|
|
John I do appreciate your input. I followed your suggestion until I hit a
problem. When I select jet 4.0 from the provider list it says MICROSOFT
DATALINK ERROR The provider is no longer available. Ensure the provider
is installed properly. I disscovered this error also occurs now in VB6.
What have I done! I did download MDAC 2.7. Was this the wrong thing to
do?? Or improper install?
eric
> Hi,
>
> Don't know what's causing the problem from the message, but I hope this
> helps out.
>
> I've downloaded the code and tested it on my system and it works fine,
> although I haven't checked the downloadable code against the book
> contents. What version of vs.net are you running? The easiest way to
> check that your system is working ok, providing you are running vs.net
> of course, is to do the following:
>
> 1) Create a new vb web app
> 2) Drag a new oledbconnection object from the toolbox onto webform1.aspx
> 2) Click the connectionstring property and create a new oledb jet4.0
> connection and choose your access database
> 3)Drag an oledbdataAdapter onto the form and use the exsiting
> connectionString and generate a simple query
> 4) Click on generate preview in the properties box and in the resulting
> dialog click fill dataset.
>
> If this generates data then you know that your environment works OK and
> you can check the resulting code to enable you to figure out what's gone
> wrong with yours. If it is down to the code in the book being incorrect
> then please let me know.
>
> Thanks
>
> John...
>
Message #5 by "John Godfrey" <jogod@b...> on Thu, 20 Sep 2001 08:53:12 +0100
|
|
Eric,
No you were quite right to install MDAC 2.7. Do you have beta 2 of
vs.net? If you do then my suggestion would be first of all to attempt to
remove it and then reinstall going through the whole process. However,
other people, myself including have had problems with incorrect
installations, and often the best solution is to just to format the disk
and start again.
Others on the list may have some better suggestions, such as checking
the DLL isn't missing, etc.
Thanks
John...
-----Original Message-----
From: ejacobse@a... [mailto:ejacobse@a...]
Sent: 20 September 2001 00:43
To: aspx_beginners
Subject: [aspx_beginners] RE: Binding to a database
John I do appreciate your input. I followed your suggestion until I hit
a
problem. When I select jet 4.0 from the provider list it says MICROSOFT
DATALINK ERROR The provider is no longer available. Ensure the provider
is installed properly. I disscovered this error also occurs now in VB6.
What have I done! I did download MDAC 2.7. Was this the wrong thing to
do?? Or improper install?
eric
> Hi,
>
> Don't know what's causing the problem from the message, but I hope
this
> helps out.
>
> I've downloaded the code and tested it on my system and it works fine,
> although I haven't checked the downloadable code against the book
> contents. What version of vs.net are you running? The easiest way to
> check that your system is working ok, providing you are running vs.net
> of course, is to do the following:
>
> 1) Create a new vb web app
> 2) Drag a new oledbconnection object from the toolbox onto
webform1.aspx
> 2) Click the connectionstring property and create a new oledb jet4.0
> connection and choose your access database
> 3)Drag an oledbdataAdapter onto the form and use the exsiting
> connectionString and generate a simple query
> 4) Click on generate preview in the properties box and in the
resulting
> dialog click fill dataset.
>
> If this generates data then you know that your environment works OK
and
> you can check the resulting code to enable you to figure out what's
gone
> wrong with yours. If it is down to the code in the book being
incorrect
> then please let me know.
>
> Thanks
>
> John...
>
$subst('Email.Unsub')
Message #6 by ejacobse@a... on Thu, 20 Sep 2001 21:31:21
|
|
I installed visual studio.net from the CD's(visualStudio.net .netFramework
(CD's 1-3) + windows componenets(1 CD) on a PC with win2000 professional,
IIS 5.0.
In fact yesterday I ran the visual studio.NET(CD's 1-3)repair/re-install
(didn't run the windows components portion though), and downloaded MDAC
2.7 and re-installed it.
I have been looking for others out on the internet with similar problems
but Haven't found any.
Stupid question, but where do the providers(specifically jet 4.0) come
from? Are they part of the operating system, do they come from
the .netFramework CD's, windows component CD, MDAC 2.7 or elsewhere??
I would appreciate help from any and all before I consider reloading my
operating system again.
I am going to
> Eric,
>
> No you were quite right to install MDAC 2.7. Do you have beta 2 of
> vs.net? If you do then my suggestion would be first of all to attempt to
> remove it and then reinstall going through the whole process. However,
> other people, myself including have had problems with incorrect
> installations, and often the best solution is to just to format the disk
> and start again.
>
> Others on the list may have some better suggestions, such as checking
> the DLL isn't missing, etc.
>
> Thanks
>
> John...
>
> -----Original Message-----
> From: ejacobse@a... [mailto:ejacobse@a...]
> Sent: 20 September 2001 00:43
> To: aspx_beginners
> Subject: [aspx_beginners] RE: Binding to a database
>
> John I do appreciate your input. I followed your suggestion until I hit
> a
> problem. When I select jet 4.0 from the provider list it says MICROSOFT
>
> DATALINK ERROR The provider is no longer available. Ensure the provider
>
> is installed properly. I disscovered this error also occurs now in VB6.
>
> What have I done! I did download MDAC 2.7. Was this the wrong thing to
>
> do?? Or improper install?
>
> eric
>
> > Hi,
> >
> > Don't know what's causing the problem from the message, but I hope
> this
> > helps out.
> >
> > I've downloaded the code and tested it on my system and it works fine,
> > although I haven't checked the downloadable code against the book
> > contents. What version of vs.net are you running? The easiest way to
> > check that your system is working ok, providing you are running vs.net
> > of course, is to do the following:
> >
> > 1) Create a new vb web app
> > 2) Drag a new oledbconnection object from the toolbox onto
> webform1.aspx
> > 2) Click the connectionstring property and create a new oledb jet4.0
> > connection and choose your access database
> > 3)Drag an oledbdataAdapter onto the form and use the exsiting
> > connectionString and generate a simple query
> > 4) Click on generate preview in the properties box and in the
> resulting
> > dialog click fill dataset.
> >
> > If this generates data then you know that your environment works OK
> and
> > you can check the resulting code to enable you to figure out what's
> gone
> > wrong with yours. If it is down to the code in the book being
> incorrect
> > then please let me know.
> >
> > Thanks
> >
> > John...
Message #7 by "John Godfrey" <jogod@b...> on Fri, 21 Sep 2001 07:31:48 +0100
|
|
Eric,
I'm not 100% on this, but I think you will find that they are part of
MDAC2.7 which is provided on the Component disk.
Thanks
John...
-----Original Message-----
From: ejacobse@a... [mailto:ejacobse@a...]
Sent: 20 September 2001 21:31
To: aspx_beginners
Subject: [aspx_beginners] RE: Binding to a database
I installed visual studio.net from the CD's(visualStudio.net
.netFramework
(CD's 1-3) + windows componenets(1 CD) on a PC with win2000
professional,
IIS 5.0.
In fact yesterday I ran the visual studio.NET(CD's 1-3)repair/re-install
(didn't run the windows components portion though), and downloaded MDAC
2.7 and re-installed it.
I have been looking for others out on the internet with similar problems
but Haven't found any.
Stupid question, but where do the providers(specifically jet 4.0) come
from? Are they part of the operating system, do they come from
the .netFramework CD's, windows component CD, MDAC 2.7 or elsewhere??
I would appreciate help from any and all before I consider reloading my
operating system again.
I am going to
> Eric,
>
> No you were quite right to install MDAC 2.7. Do you have beta 2 of
> vs.net? If you do then my suggestion would be first of all to attempt
to
> remove it and then reinstall going through the whole process.
However,
> other people, myself including have had problems with incorrect
> installations, and often the best solution is to just to format the
disk
> and start again.
>
> Others on the list may have some better suggestions, such as checking
> the DLL isn't missing, etc.
>
> Thanks
>
> John...
>
> -----Original Message-----
> From: ejacobse@a... [mailto:ejacobse@a...]
> Sent: 20 September 2001 00:43
> To: aspx_beginners
> Subject: [aspx_beginners] RE: Binding to a database
>
> John I do appreciate your input. I followed your suggestion until I
hit
> a
> problem. When I select jet 4.0 from the provider list it says
MICROSOFT
>
> DATALINK ERROR The provider is no longer available. Ensure the
provider
>
> is installed properly. I disscovered this error also occurs now in
VB6.
>
> What have I done! I did download MDAC 2.7. Was this the wrong thing
to
>
> do?? Or improper install?
>
> eric
>
> > Hi,
> >
> > Don't know what's causing the problem from the message, but I hope
> this
> > helps out.
> >
> > I've downloaded the code and tested it on my system and it works
fine,
> > although I haven't checked the downloadable code against the book
> > contents. What version of vs.net are you running? The easiest way
to
> > check that your system is working ok, providing you are running
vs.net
> > of course, is to do the following:
> >
> > 1) Create a new vb web app
> > 2) Drag a new oledbconnection object from the toolbox onto
> webform1.aspx
> > 2) Click the connectionstring property and create a new oledb jet4.0
> > connection and choose your access database
> > 3)Drag an oledbdataAdapter onto the form and use the exsiting
> > connectionString and generate a simple query
> > 4) Click on generate preview in the properties box and in the
> resulting
> > dialog click fill dataset.
> >
> > If this generates data then you know that your environment works OK
> and
> > you can check the resulting code to enable you to figure out what's
> gone
> > wrong with yours. If it is down to the code in the book being
> incorrect
> > then please let me know.
> >
> > Thanks
> >
> > John...
$subst('Email.Unsub')
Message #8 by "Carl Schneider" <cschneider@i...> on Tue, 25 Sep 2001 21:50:53
|
|
I can't help you much on V.S. but the answer to your data provider
question is no they are not part of the operating system.
Data providers are classes provided from Microsoft and other data engine
developers to provide programatic access to a specific data platform.
Providers developed by Microsoft are part of the MDAC (Microsoft Data
Access Components) packs and may or may not be updated with each MDAC
release.
The idea behind the MDAC releases are to abstract the nuances of
individual data platforms by providing a consistant programming interface
for manipulating all of them.
Think of it like this...
If ADO is the front end of data access and SQL, Oracle, or Access is the
back end then ODBC and Data Providers are the middle men that tie the
front to the back.
I hope that helped.
Message #9 by ejacobse@a... on Wed, 26 Sep 2001 01:08:07
|
|
Just wanted to say thanks for your input on my "rough spot". My
resolution was to uninstall IIS 5.0 and visual studio.net, then run a
clean install of win 2000 pro(didn't delete the partition, but I ended up
OK). Re-installed IIS 5.0, windows components(includes MDAC 2.7), and
visual studio.NET and was able to select my jet 4.0 provider and run the
test you had suggested. All is working! Thanks alot.
eric
Message #10 by ejacobse@a... on Wed, 26 Sep 2001 01:09:43
|
|
Thanks for the knowledge on MDAC. I appreciate your info.
eric
> I can't help you much on V.S. but the answer to your data provider
> question is no they are not part of the operating system.
>
> Data providers are classes provided from Microsoft and other data engine
> developers to provide programatic access to a specific data platform.
> Providers developed by Microsoft are part of the MDAC (Microsoft Data
> Access Components) packs and may or may not be updated with each MDAC
> release.
>
> The idea behind the MDAC releases are to abstract the nuances of
> individual data platforms by providing a consistant programming
interface
> for manipulating all of them.
>
> Think of it like this...
>
> If ADO is the front end of data access and SQL, Oracle, or Access is
the
> back end then ODBC and Data Providers are the middle men that tie the
> front to the back.
>
> I hope that helped.
|
|
|
View Cart
