By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,109 Members | 969 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,109 IT Pros & Developers. It's quick & easy.

OleDbException executing reader on Access stored view

P: n/a
I had a strange error in asp.net when try to execute a simple select
statement like "Select * From ViewName" if the stored view contains a where
clause.
The connection is made to an Access database using System.Data.OleDb objects
and Jet 4.0 oledb provider.
The same code works fine in windows form application.
Removing the where clause from the stored view or adding ASPNET user into
"Power Users" or "Administrators" groups, all works also in asp.net.
My first idea was a security/permission problem, but it is strange that all
properly works without the where clause.

The error happens on Win xp sp2 with .NET 1.1 sp1 and don't happens on Win
xp sp1 with .NET 1.1 sp1.

???????
Some ideas?

Thanks so much for your help, Marco.
Nov 19 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Exceptions have messages. Odd that you danced all around the exception
without managing to mention what exactly it IS. How about it?

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.

"Marco Frontini" <iu******@libero.it> wrote in message
news:uc****************@TK2MSFTNGP10.phx.gbl...
I had a strange error in asp.net when try to execute a simple select
statement like "Select * From ViewName" if the stored view contains a
where clause.
The connection is made to an Access database using System.Data.OleDb
objects and Jet 4.0 oledb provider.
The same code works fine in windows form application.
Removing the where clause from the stored view or adding ASPNET user into
"Power Users" or "Administrators" groups, all works also in asp.net.
My first idea was a security/permission problem, but it is strange that
all properly works without the where clause.

The error happens on Win xp sp2 with .NET 1.1 sp1 and don't happens on Win
xp sp1 with .NET 1.1 sp1.

???????
Some ideas?

Thanks so much for your help, Marco.

Nov 19 '05 #2

P: n/a
A generic "Internal OLE Automation Error" isn't so usefull.
"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> ha scritto nel messaggio
news:O8****************@TK2MSFTNGP10.phx.gbl...
Exceptions have messages. Odd that you danced all around the exception
without managing to mention what exactly it IS. How about it?

--
HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
Neither a follower nor a lender be.

"Marco Frontini" <iu******@libero.it> wrote in message
news:uc****************@TK2MSFTNGP10.phx.gbl...
I had a strange error in asp.net when try to execute a simple select
statement like "Select * From ViewName" if the stored view contains a
where clause.
The connection is made to an Access database using System.Data.OleDb
objects and Jet 4.0 oledb provider.
The same code works fine in windows form application.
Removing the where clause from the stored view or adding ASPNET user into
"Power Users" or "Administrators" groups, all works also in asp.net.
My first idea was a security/permission problem, but it is strange that
all properly works without the where clause.

The error happens on Win xp sp2 with .NET 1.1 sp1 and don't happens on
Win xp sp1 with .NET 1.1 sp1.

???????
Some ideas?

Thanks so much for your help, Marco.


Nov 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.