Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Dbase connectivity...
- Thread starter Isadore
- Start date
- Thread starter
- #3
Nat:
Have decided, without explicit information, to use one mdb with several tables; not doing that much initially - was just wondering if having, say, 3 mdb's in the root web directory, whether that would lower the probability of opening and closing one database at any particular time causing a conflict.
Right now I have other problems - and have been discussing with Zarc.
I have spent the last 16 hours trying to "connect" to an mdb using OLE DB connectivity -- so stopped cold in .NET development right out of the shute.
I can't get pass the "PERMISSION" problem with Access. All is working but when I try to bind, say, a DataGrid, I can never populate it because an exception error occurs saying I don't have permission to open the Access database.
Seems I have tried everything, putting the ".mdw" file in the root web directory, etc. etc... so struggling right now. If I could just get some data bound I could take off and finish some web pages -- was trying to get something done before an annual picknic coming up on June 6th.
Any ideas here? I have several books on .NET but all assume one has permission to open the database. Behind .NET no problem, all data review, etc.. opens up the tables with no problem, but when I open up the web form the code always stops at the "fill" code saying I don't have Permission to continue. I can't believe this has been that difficult --- I have been dying to get going with .NET but have been stopped cold at the very beginning.
Thanks for taking the time.
Have decided, without explicit information, to use one mdb with several tables; not doing that much initially - was just wondering if having, say, 3 mdb's in the root web directory, whether that would lower the probability of opening and closing one database at any particular time causing a conflict.
Right now I have other problems - and have been discussing with Zarc.
I have spent the last 16 hours trying to "connect" to an mdb using OLE DB connectivity -- so stopped cold in .NET development right out of the shute.
I can't get pass the "PERMISSION" problem with Access. All is working but when I try to bind, say, a DataGrid, I can never populate it because an exception error occurs saying I don't have permission to open the Access database.
Seems I have tried everything, putting the ".mdw" file in the root web directory, etc. etc... so struggling right now. If I could just get some data bound I could take off and finish some web pages -- was trying to get something done before an annual picknic coming up on June 6th.
Any ideas here? I have several books on .NET but all assume one has permission to open the database. Behind .NET no problem, all data review, etc.. opens up the tables with no problem, but when I open up the web form the code always stops at the "fill" code saying I don't have Permission to continue. I can't believe this has been that difficult --- I have been dying to get going with .NET but have been stopped cold at the very beginning.
Thanks for taking the time.
Isadore,
I would check the file permissions on your database file. Right-click on the database go to properties and then click security tab. Make sure that the Users group has atleast read access and maybe the following too depending on what you are doing (write, modify, execute).
I would check the file permissions on your database file. Right-click on the database go to properties and then click security tab. Make sure that the Users group has atleast read access and maybe the following too depending on what you are doing (write, modify, execute).
- Thread starter
- #5
duct:
Thanks. Spent a lot of time on this problem; and I knew it was probably going to be an error on my part; obviously, and it turned out that I did not properly configure Front Page Server before I installed VStudio.
Its times like that that are killers!
Appreciate you getting back. I'll be postings odds and ends here and there as I develop skills in VB.NET.
Thanks. Spent a lot of time on this problem; and I knew it was probably going to be an error on my part; obviously, and it turned out that I did not properly configure Front Page Server before I installed VStudio.
Its times like that that are killers!
Appreciate you getting back. I'll be postings odds and ends here and there as I develop skills in VB.NET.
- Thread starter
- #6
duct: One other note to close this session.
My strategy will be to have a "Server" database set of tables much unlike the main database tables -- i.e., I don't want the Server doing anything it doesn't have to do, so I will present the Server with tables designed to open and close as quickly as possible -- minimizing time, etc...
Also, I am going to just use one *.mdb file (we expect no more than say 200-300 visitors a day) --
My strategy will be to have a "Server" database set of tables much unlike the main database tables -- i.e., I don't want the Server doing anything it doesn't have to do, so I will present the Server with tables designed to open and close as quickly as possible -- minimizing time, etc...
Also, I am going to just use one *.mdb file (we expect no more than say 200-300 visitors a day) --
- Status
Similar threads
