Home
|
Forums
|
Contact
|
Search
|
Syndication
[login]
[create account]
Friday, August 29, 2025
slxdeveloper.com
Home
Search
Contact us
About slxdeveloper
Syndication
Community
Forums
(NEW!)
Newsletter Archive
Members
Your Profile
Submit Article
General
Administration
(6)
OLE DB Provider
Miscellaneous
(2)
Architect
VBScript
(9)
ActiveX Controls
(6)
How To's
(14)
.NET Extensions
(3)
External
OLE DB Provider
(12)
SLAPI (SlgxApi.dll)
SalesLogix COM
(1)
Web
ASP/ASP.NET
(2)
Web Services
Web Client
Downloads
Samples
(17)
Documentation
(7)
Utilities
(18)
Resources
SalesLogix
(3)
Programming
(1)
8/29/2025 1:33:37 PM
slxdeveloper.com Community Forums
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Architect Forums - SalesLogix Scripting & Customization
Forum to discuss writing script in Architect plugins for SalesLogix & general SalesLogix customization topics
(for Windows client only)
. View the
code of conduct
for posting guidelines.
Forums RSS Feed
Back to Forum List
|
Back to SalesLogix Scripting & Customization
|
New Thread
View:
Dynamic
Flat
Tree
Search:
Author
Thread: Anyone connected to SLX via Perl successfully?
thepip3r
Posts: 16
Anyone connected to SLX via Perl successfully?
Posted: 11 Sep 09 3:36 PM
I'm having trouble connecting to SLX via Perl because I can't figure out how to pass the connectionString information. With previous help from the forum members, I was very successfully able to connect and pull queries with VBS but havne't been able to with PERL using DBI modules and Win32::OLE. Does anyone have a code example of a successful slx db connection using perl and the slxoledb.1 provider?? All assistance is greatly appreciated.
have tried:
[code]use Win32::OLE;
use Win32::OLE::Const 'Microsoft ActiveX Data Objects';
$Conn = Win32::OLE->new("ADODB.Connection");
$RS = Win32::OLE->new("ADODB.Recordset");
$DSN = "Provider=SLXOLEDB.1;Integrated Security=True;Initial Catalog=SLXDB;Data Source=SLXHOST;Extended Properties=PORT=1706;LOG=ON;Location=;Mode=Read;";
$Conn->OPEN( $DSN ) or die("Failed to connect with " . $DSN);
$sql = "SELECT TOP 1 T.ALTERNATEKEYPREFIX,T.ALTERNATEKEYSUFFIX,C.LASTNAME,C.FIRSTNAME,C.EMAIL FROM sysdba.TICKET T JOIN sysdba.CONTACT C ON T.CONTACTID = C.CONTACTID WHERE T.ALTERNATEKEYSUFFIX = '001-00-026651'";
$RS = $Conn->execute($sql);
until ($RS->EOF) {
my $field1 = $RS->Fields("FIRSTNAME")->value;
print "$field1";
$RS->MoveNext;
}
$RS->Close;
$Conn->Close;[/code]
but no worky. any help would be appreciated. i actually get an error on line 8 which is the $Conn->OPEN line. I've taken out the rest of the fluff and just left in the $Conn->Open but I continually fail to connect successfully.
[
Reply
][
Quote
]
Ryan Farley
Posts: 2265
Re: Anyone connected to SLX via Perl successfully?
Posted: 11 Sep 09 4:48 PM
Your problem is likely the integrated security. Have you tried explicitly specifying a username and password in the connection string?
[
Reply
][
Quote
]
thepip3r
Posts: 16
Re: Anyone connected to SLX via Perl successfully?
Posted: 15 Sep 09 4:32 PM
Ryan,
Thanks for the info. You were 100% correct. The connection string was updated as follows (I'm including it for any future SLX Perl-scripters):
use Win32::OLE;
use Win32::OLE::Const 'Microsoft ActiveX Data Objects';
my $Conn = Win32::OLE->new("ADODB.Connection");
my $RS = Win32::OLE->new("ADODB.Recordset");
$DSN = "Provider=SLXOLEDB.1;Integrated Security=SSPI;Initial Catalog=SLXSUPPORT;Data Source=slx;Extended Properties=PORT=1706;LOG=ON;Location=;Mode=Read;";
$Conn->Open( $DSN );
[
Reply
][
Quote
]
Page 1 of 1
You can subscribe to receive a daily forum digest in your
user profile
. View the site
code of conduct
for posting guidelines.
Forum RSS Feed
-
Subscribe to the forum RSS feed to keep on top of the latest forum activity!
slxdeveloper.com is brought to you courtesy of
Ryan Farley
&
Customer FX Corporation
.
This site, and all contents herein, are Copyright © 2025 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.
code of conduct
|
page cache (param): 8/29/2025 2:10:55 PM