10/31/2024 6:53:13 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!
Forum to discuss using the SalesLogix OLE DB Provider from external applications (including usage of built-in provider procedures). View the code of conduct for posting guidelines.
|
|
|
|
OLEDB from SLAPI
Posted: 01 Feb 07 9:14 AM
|
fiogf49gjkf0d Hi,
I'm both very new to Saleslogix and slxdeveloper.com and am almost bald now after inheriting our 5 year old VB code.
Just to explain, 2 weeks ago we upgraded from SLX 5.2 (I think) to 6.2, which we are still having fun with. However the problem I am experiencing involves a VB6 program, which is basically meant to create an account "without" using any of the SLX screens, or at the very least setting a a client account to active (that might be something we have internally though).
Now in the past this has used the slapi_logInto function just to get the connection, since the upgrade this no longer works, so as a first question, I know I need to move it to OLEDB, but how should I do this as any reference material is very thin on the ground and the material I have found seems to indicate that this should still work, I have spoken to the DBA and the Alias is set up and running fine. In addition to this I downloaded the SLX SDK V6 sample which also uses this function AND produces the same error return as the VB I have inherited.
Both return error 31, which when put through the errortext function returns a rather descriptive "0: 31"!!
Any help would be most appreciated.
Thanks
Wayne |
|
|
| |
|
Re: OLEDB from SLAPI
Posted: 02 Feb 07 9:57 AM
|
fiogf49gjkf0d SLAPI should still work with v6.2, although it sucks  You'd need to change the code so it uses an OLEDB alias (as configured on the login screen on the client) instead of a BDE alias.
Rewriting it to use the SLX OLEDB provider would be the way to go. As Carla pointed out there's some articles on this site that should give some basics, however you're just writing to the database just as you would with any OLEDB provider. It is just standard ADO, no wierd calls to things like slapi_DBSetValue etc. The only really SLX specific thing is the connection string so it will use the SLX OLEDB provider. |
|
|
|
Re: OLEDB from SLAPI
Posted: 02 Feb 07 10:13 AM
|
fiogf49gjkf0d Hi again,
Thanks for the replys, I believe we are using the Alias from the login screen which is, probably a bit unoriginal, "SALESLOGIX", our suppliers are also saying it should work, however we still get this mysterious error 31 returned from the loginto attempt, the suppliers also mention something about the ADOAlias.ini file, but from my investigations in the reference guides this is an alternative to using the Alias in the Data Link Manager.
We did have trouble with permissions after the upgrade initially, so I am wondering if this is another knock on from the security changes and nothing to do with the program at all!! |
|
|
|
Re: OLEDB from SLAPI
Posted: 02 Feb 07 10:34 AM
|
fiogf49gjkf0d The error 31 is an ambiguous error that can mean many things. The most common place you'll see that is when using the SLAPI from a service context (windows service, web application, etc). It just isn't meant to do that and is very picky on permissions etc.
Could this be your scenario?
If so, I'd not every try to get it working again and would just bite the bullet and rewrite to use OLEDB. |
|
|
|
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!
|
|
|
|
|
|
|
|