May 10, 2004 at 1:27 pm
I'm looking for a list of OLE DB connection string parameters for SQL Server 2000 (SQLOLEDB provider).
I'm connecting to a SQL Server 2000 SP3a database from Powerbuilder 8 using OLE DB. I can't seem to get the application name to show up in sysprocesses.program_name. My connection string contains the following:
PROVIDER='SQLOLEDB',Application Name='MyApp',
DATASOURCE='MyServer',PROVIDERSTRING='database=MyDB'
Anybody know the correct syntax/spelling for "Application Name=" ?
( An ADO example for VB would be ok )
Thanks,
Mike
May 10, 2004 at 1:53 pm
This site is great for getting ADO connection strings to multiple dbs.
http://www.able-consulting.com/ADO_Conn.htm
A better one for applpication name is contained in:
Hope either helps.
May 11, 2004 at 2:46 am
Sometimes applications force the appname to say Powerbuilder etc. and dont allow you to set this attribute, one way round this is to use a file dsn and set the app name in there.
Phil Nicholas
May 12, 2004 at 3:27 am
Tried a few combinations and finally found it.
Syntax is:
App=application_name
No spaces between the equal sign. I tried this in a vb package and ms access and both work.
November 19, 2004 at 12:55 pm
I am trying this from an Access2003 adp without success.
strConnect = "Provider=SQLOLEDB.10;Server=Server;Initial Catalog=MyDB;UID=Me;Pwd=Mine;App=MyCustomString;"
Does the order matter in the connection string? Any suggestions?
November 28, 2004 at 3:55 pm
Dunno if you've solved this yet, but I'm connecting from PowerBuilder 9 using OLEDB and the following connection string and I'm successfully setting the application name:
Provider='SQLOLEDB',DataSource='myserver',Database='mydbname',PROVIDERSTRING='App=myappname',IntegratedSecurity='SSPI'
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy