I have a Visual Basic .Net front-end to a Microsoft Access back-end. The Back-end is stored on a network share and during development, all of which took place on my desktop system, things went fine. The program uses an ADO connection to the database with the line
Dim conn As New OleDb.OleDbConnection( _
"Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=" & _
"\\networkshare\mydb.mdb")
This worked just fine. Now, however, I want to distribute this EXE to the end users and enable them to run it over a network. When I run it from the network, however, I receive the error message:
JIT Debugging failed with the following error: 0x800405a6
Please check the documentation topic 'Just-in-time debugging errors' for more information.
Well, I did some digging on these very forums and found that it is a security issue and I was able to resolve this by going into Administrative Tools -> .NET Wizards -> Adjust .NET Security and setting Local Intranet to "Full". Now it runs fine on my system, but this doesn't fix my problem.
This application will be run on dozens of systems across several sites where the users' computer policy does not enable them to even view Administrative Tools in their Control Panels. Thus, they are locked out. Having all of them copy the EXE file to their desktops is equally not an option.
Can someone please show me a solution to this problem?
BTW, I'm certain the problem lies in my database access, as I have commented the lines out and executed and it goes just fine, so the breech of the security policy is directly linked to the ADO.
THANK YOU...PLEASE help me. I can't have wasted all this development time.
Dim conn As New OleDb.OleDbConnection( _
"Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=" & _
"\\networkshare\mydb.mdb")
This worked just fine. Now, however, I want to distribute this EXE to the end users and enable them to run it over a network. When I run it from the network, however, I receive the error message:
JIT Debugging failed with the following error: 0x800405a6
Please check the documentation topic 'Just-in-time debugging errors' for more information.
Well, I did some digging on these very forums and found that it is a security issue and I was able to resolve this by going into Administrative Tools -> .NET Wizards -> Adjust .NET Security and setting Local Intranet to "Full". Now it runs fine on my system, but this doesn't fix my problem.
This application will be run on dozens of systems across several sites where the users' computer policy does not enable them to even view Administrative Tools in their Control Panels. Thus, they are locked out. Having all of them copy the EXE file to their desktops is equally not an option.
Can someone please show me a solution to this problem?
BTW, I'm certain the problem lies in my database access, as I have commented the lines out and executed and it goes just fine, so the breech of the security policy is directly linked to the ADO.
THANK YOU...PLEASE help me. I can't have wasted all this development time.