G
Guest
Hello.
I'm an old VB6 programmer who would like to distribute an .exe with the
simplest method possible, and that's not working.
I have an application which updates rows on a SQL Server. If I run the .exe
in my project's debug folder, it runs fine. If I run it from my project's
release folder, I get a sqlClientPermission error when it tries to update
data on the server.
I don't have administrative rights to my PC, so I'm assuming I have to live
with this or find someone with admin rights to grant me permission to run the
release version of my application on my PC.
If I run it copied to a folder on the network, I get the same error, but
what I really need is for it to run in a DTS package on our SQL Server so it
can be scheduled to run nightly.
The release .exe gets the same error in the DTS package, and I'm not sure
who needs to do what to get this to work. The debug.exe runs ok in the DTS
package as long as my sps have dbo ownership.
I'm not sure if I need to create a setup project and have the DBA install
the .exe on the sql server, have some administrator (not our DBA) grant
client access permissions to my .exe on the sql server, or some other set of
magic tricks.
Distributing applications used to be easy, but now it's harder and muddling
through documentation on code access security is frying my brain.
Please help me if you can.
Thanks for all replies,
-Beth
I'm an old VB6 programmer who would like to distribute an .exe with the
simplest method possible, and that's not working.
I have an application which updates rows on a SQL Server. If I run the .exe
in my project's debug folder, it runs fine. If I run it from my project's
release folder, I get a sqlClientPermission error when it tries to update
data on the server.
I don't have administrative rights to my PC, so I'm assuming I have to live
with this or find someone with admin rights to grant me permission to run the
release version of my application on my PC.
If I run it copied to a folder on the network, I get the same error, but
what I really need is for it to run in a DTS package on our SQL Server so it
can be scheduled to run nightly.
The release .exe gets the same error in the DTS package, and I'm not sure
who needs to do what to get this to work. The debug.exe runs ok in the DTS
package as long as my sps have dbo ownership.
I'm not sure if I need to create a setup project and have the DBA install
the .exe on the sql server, have some administrator (not our DBA) grant
client access permissions to my .exe on the sql server, or some other set of
magic tricks.
Distributing applications used to be easy, but now it's harder and muddling
through documentation on code access security is frying my brain.
Please help me if you can.
Thanks for all replies,
-Beth