Recent content by arniec

Thank you thank you thank you!!!! That worked, and your explanation has allowed me to modify it to fit another scenario as well. THANK YOU!

I am running SQL Server 2000. I have a field which comes in as a string of numbers representing a date. For example: 122506 is christmas of this year. 70406 is the 4th of July. I need to get this information stored in a DateTime field in the database. I was hoping to write a stored...

Works wonderfully, THANK YOU!

That code is very interesting. I have some other cases where it will come in quite handy, but it appears to be using code to do this. Can these connections be used to create linked tables in Access? Thank you!!!!!!!!!! I appreciate you taking the time to help me.

I have a SQL server set up and want to create an Access Database which will reside on a network share and hit the SQL Server. It is pointing to the SQL server through an ODBC connection. This database will be used by dozens of people; is there any way to get it set up where I do not have to...

Yeah, even with the Integrated Security I get an error from the network, and it workes fine from the desktop. I'm looking more into the "copy the file" solution. It may be the best/only way (packaging is not really an option) One question: if I have A.EXE on someone's C drive and they launch...

Dim conn As New SqlClient.SqlConnection("Data Source = D3HTT321; Initial Catalog = d_alt_lending") conn.Open() msgbox "It opened." conn.Close() msgbox "It closed."

Rick, I tried the SQL Server option and still hit the same security issue, and it's not trying to pop an LDB file. I made a quick app which connects to our SQL Server (the code is above) and it bombed.

Rick, Thanks for the suggestion. I tried it and a mapped network drive didn't fix the solution; the .NET framework still treated it as a network location.

Given this, mwardle, is there any way to rewrite the code to do the same thing in a way that would not alert the .NET security? Any other connection object or such that will fly "under the radar" so to speak?

I tried the "quickie application" route. I tried connecting to one of our existing SQL Servers and received the exact same security exception. I had this code: Dim conn As New SqlClient.SqlConnection("Data Source = D3HTT321; Initial Catalog = d_alt_lending") conn.Open() and...

One other thing: are we SURE that moving to SQL Server will fix the problem? Can I get verification that at the default level of security for the .Net 1.1 Framework allows this? I'd hate to spend a day rewriting this (it would be less for a more experienced .Net programmer I'm sure but I'm...

Macleod, In its own class? No. But still not that hard to change. The problem here lies in the fact that the domain accounts are managed by another group who doesn't like to talk to us much; all our current SQL users must be added manually by us. This could still possibly work, but in all...

The more I think about it, this option probably won't be as easy as I'd hoped as then I'd have to grant these users access to the SQL server, and the user base changes on a daily basis; there's no way to know the domain logins of all the users who will need this access. also, the systems are...

Bob, I can move the database out of Access and into SQL easily enough, but will the same code then function? I have Dim conn As New OleDb.OleDbConnection( _ "Provider=Microsoft.Jet.OLEDB.4.0;" & _ "Data Source=" & _ "\\networkshare\somefile.mdb") If I...