You're not giving us quite enough information here - the main thing being what version of SalesLogix this is. If you're upgrading a package from SQL 2005, then I doubt you're dealing with SalesLogix 8.x, but if you're using SQL 2012 on anything less than SalesLogix 8.x you're probably not going to get it to work, period. As for the script code, I assume you've tried the standard way of doing it from SQL 2005-2008, i.e., casting:
Dim SLXConnection As System.Data.OleDb.OleDbConnection SLXConnection = CType(Connections.SalesLogix.AcquireConnection(Nothing), System.Data.OleDb.OleDbConnection) SLXConnection.Open()
...where the "SalesLogix" connection in the ScriptTask component uses the SLX provider listed under "OLEDB wrappers for ADO.NET," not the native OLEDB driver? Or is that not even available?
Also, when you say you want the "new productid," does that mean you want to create a new PRODUCT record for which you need to generate a new ID, or are you just looking to read new PRODUCT records as they come in from some other source?
Lastly, you should be able to get the same effect as hard-coding the connection string by storing the connection string in an object-level variable and then reading that variable into your script from a secured configuration file. It's a perfectly valid way to do it... whatever works! |