|
-
Oct 10th, 2003, 02:52 AM
#1
Thread Starter
Fanatic Member
-
Oct 10th, 2003, 03:05 AM
#2
Frenzied Member
Hmm, I don't think there is. In saying that, if all your connection code is in a module / class, then you could just add a DSN-less connection which would solve your problem.
I don't know the extent of your program and therefore don't know how much work this would be for you.
Mega.
"If at first you don't succeed, then skydiving is not for you"
-
Oct 10th, 2003, 03:13 AM
#3
Thread Starter
Fanatic Member
then you could just add a DSN-less connection which would solve your problem.
Could you be a bit more explicit!!
All the security information is stored in a *.ini file......You will have to excuse my ignorance but Would I still need to create a DSN if
the information is stored in a INI file? the application needs to be installed on a approx. 100 PC's... if the answer to the above is
YES then I dont fancy installing a DSN on every PC....
** HOLLY ** 
-
Oct 10th, 2003, 03:18 AM
#4
Frenzied Member
VB Code:
Connection.Open "Driver={SQL Server};" & _
"Server=MyServerName;" & _
"Database=myDatabaseName;" & _
"Uid=myUsername;" & _
"Pwd=myPassword"
This is an example that doesn't need a DSN. You can still have your SQL server IP in the INI file and use what it returns in the above example.
Mega.
"If at first you don't succeed, then skydiving is not for you"
-
Oct 10th, 2003, 03:20 AM
#5
Thread Starter
Fanatic Member
-
Oct 10th, 2003, 06:19 PM
#6
Frenzied Member
No problem
Glad I could help.
Mega.
"If at first you don't succeed, then skydiving is not for you"
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|