Accessing a password protected MS Access File
-
Hmm, didn't really help there since I am using the oledbdataadapter wizard to link to my MS Access file.. Anyone else who got any idea to my situation..? Thanz anyway, Dave. P.S :- You mentioned that u are not using Access years ago... What are you using now to keep your data and all.. Can it be password protected? If so, I might want to look into it...
-
You said the database is password protected. How is it protected? In Access there are 2 ways to protect a database. 1 is by setting the database password (this will simply prompt for a password when you try to open the db), the other is by setting up users and using a workgroup database to store this info. How you access the DB in code will depend on which method used. Jon
-
icowa wrote: Is there no one who can help me on this area? Have patience. You got an initial reply in 4 hours and you posted this after 8 hours. That isn't too bad considering how much this service is costing you (i.e. nothing). Everyone who responds here are volunteers. If you need a fast solution to your problem then you can always open a support incident with Microsoft. Anyway, to your problem. First, try not to use the wizards - if you feel you must, at least look at the code they generate. You can look at the code the wizard generates and modify the connection string. Dave already suggested one. You can find more examples at http://www.connectionstrings.com/[^]
My: Blog | Photos WDevs.com - Open Source Code Hosting, Blogs, FTP, Mail and More
-
Hmm, didn't really help there since I am using the oledbdataadapter wizard to link to my MS Access file.. Anyone else who got any idea to my situation..? Thanz anyway, Dave. P.S :- You mentioned that u are not using Access years ago... What are you using now to keep your data and all.. Can it be password protected? If so, I might want to look into it...
If your using the Wizard to generate the OleDb code, then I think you're out of luck using a password protected Access database. I found the code the Wizards generated to much of a pain to maintain, so I would HIGHLY recommend writing the code by hand. It's much easier to maintain, by FAR, much easier to ask questions about in the forums, much easier to debug, and it gives you much greater control over how your code runs. I use MSDE and SQL Server. Both of which has security FAR better than anything you'll find in Access. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
icowa wrote: Is there no one who can help me on this area? Have patience. You got an initial reply in 4 hours and you posted this after 8 hours. That isn't too bad considering how much this service is costing you (i.e. nothing). Everyone who responds here are volunteers. If you need a fast solution to your problem then you can always open a support incident with Microsoft. Anyway, to your problem. First, try not to use the wizards - if you feel you must, at least look at the code they generate. You can look at the code the wizard generates and modify the connection string. Dave already suggested one. You can find more examples at http://www.connectionstrings.com/[^]
My: Blog | Photos WDevs.com - Open Source Code Hosting, Blogs, FTP, Mail and More
:doh: I completely forgot about that site! Thanks Colin! RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
You said the database is password protected. How is it protected? In Access there are 2 ways to protect a database. 1 is by setting the database password (this will simply prompt for a password when you try to open the db), the other is by setting up users and using a workgroup database to store this info. How you access the DB in code will depend on which method used. Jon
-
If your using the Wizard to generate the OleDb code, then I think you're out of luck using a password protected Access database. I found the code the Wizards generated to much of a pain to maintain, so I would HIGHLY recommend writing the code by hand. It's much easier to maintain, by FAR, much easier to ask questions about in the forums, much easier to debug, and it gives you much greater control over how your code runs. I use MSDE and SQL Server. Both of which has security FAR better than anything you'll find in Access. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
mmm, I was afraid you'll say that. The part about vb.net not being able to access a password protected Access file. Yea, I read a lot of PDF files on this sql but not a one of them is very intuitive on how you go and create a SQL Db and accessing it and providing it with password and all. Thats what made me go and figure out on Access on the first place. Since I search throughout the net before and not having much luck, do you know of any sites or maybe you have any PDF files that is good in teaching u on SQL. Preferably with good DIY step by step instructions... Thanz
-
mmm, I was afraid you'll say that. The part about vb.net not being able to access a password protected Access file. Yea, I read a lot of PDF files on this sql but not a one of them is very intuitive on how you go and create a SQL Db and accessing it and providing it with password and all. Thats what made me go and figure out on Access on the first place. Since I search throughout the net before and not having much luck, do you know of any sites or maybe you have any PDF files that is good in teaching u on SQL. Preferably with good DIY step by step instructions... Thanz
icowa wrote: The part about vb.net not being able to access a password protected Access file. I didn't say it couldn't access a password protected Access file. I said it wasn't supportable in the forums because the Wizard is completely visual. It's FAR easier to deal with code that is hand written then it is to deal with the stuff that the Wizard generates. icowa wrote: Since I search throughout the net before and not having much luck, do you know of any sites or maybe you have any PDF files that is good in teaching u on SQL. Preferably with good DIY step by step instructions I don't have anything. I taught myself SQL Server straight out of the Administrators manuals. There's no such thing as adding a single password to an SQL Server database. Each SQL Server can maintain it's own users and groups. You can give each user/group rights to specific databases, tables, procedures, ... Right down to even who can execute which procedures and who can can cannot read/write whatever tables in the databases. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
icowa wrote: The part about vb.net not being able to access a password protected Access file. I didn't say it couldn't access a password protected Access file. I said it wasn't supportable in the forums because the Wizard is completely visual. It's FAR easier to deal with code that is hand written then it is to deal with the stuff that the Wizard generates. icowa wrote: Since I search throughout the net before and not having much luck, do you know of any sites or maybe you have any PDF files that is good in teaching u on SQL. Preferably with good DIY step by step instructions I don't have anything. I taught myself SQL Server straight out of the Administrators manuals. There's no such thing as adding a single password to an SQL Server database. Each SQL Server can maintain it's own users and groups. You can give each user/group rights to specific databases, tables, procedures, ... Right down to even who can execute which procedures and who can can cannot read/write whatever tables in the databases. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
No, you learn how to write the code yourself instead of having a Wizard mess it up for you. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome