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!
|
|
External Data in Support Client
Posted: 11 May 06 10:33 AM
|
zoloft pregnancy risk zoloft and pregnancy first trimester fiogf49gjkf0d Has anyone successfully displayed data from an external database in
the support client? I have code working in the sales client. 6.2.3
The same code in the support client yields the following error message.
"Arguments are of the wrong type, are out of acceptable range, or are
in conflict with one another"
Here is the code. The message references the objRS.open line.
Sub AXFormOpen(Sender)
set objConn = CreateObject("ADODB.Connection")
objConn.Open strProvider
End Sub
Sub AXFormChange(Sender)
Set objRS = CreateObject("ADODB.Connection")
objRS.LockType = adLockBatchOptimistic
objRS.CursorType = adOpenDynamic
objRS.CursorLocation = 3 ''client side
objRS.open strSQL, objConn
Thanks for any assistance.
Daryl Probetts
|
|
|
| |
|
Re: External Data in Support Client
Posted: 17 May 06 2:05 PM
|
fiogf49gjkf0d I don't ever use the Support Client so I don't know for sure, but perhaps the ADO constants are not defined there. Change the ADO constants to their numeric equivalents.
adLockBatchOptimistic = 4
adOpenDynamic = 2
(I think) |
|
|
| |
|
Re: External Data in Support Client
Posted: 22 May 06 2:49 PM
|
buy amoxicillin online buy amoxicillin canada blog.endungen.de antibiotic without prescription fiogf49gjkf0d Nothing jumps out as wrong from the code itself, could there be a problem with the connection string? |
|
|
|
Re: External Data in Support Client
Posted: 23 May 06 9:14 AM
|
abortion pill usa legal abortion pill online usa fiogf49gjkf0d The same connection string works in the Sales client. In fact, I used your utility to get the connection string. Thanks for the utility. |
|
|
|
Re: External Data in Support Client
Posted: 23 May 06 11:12 AM
|
fiogf49gjkf0d Why not use Application.GetNewConnection? It returns a connection string from the client without the need of a utility. What you may want to do is MsgBox debug GetNewConnection vs your connection string to see if there are any differences.
When I look at the stock SalesLogix code, the only Support forms I see are Legacy. I'm taking a stab here but it's possible that the support client wasn't updated to handle VBScript but still relies on heavy Legacy code to function properly. Legacy can still call COM objects so I would think you could still use ADO recordsets you would just need to approach it with Legacy variables instead of VBScript.
If this is true, Support client has turned into the red-headed step child. I suppose that's why it was merged into the Sales client and all Active Forms were created to handle it. The Legacy forms should just work so them creating all new ones for the Sales side may say something about all of this. |
|
|
|
Re: External Data in Support Client
Posted: 23 May 06 5:47 PM
|
mixing melatonin and weed mixing melatonin and weed fiogf49gjkf0d I think Jeremy might have hit it on the head. Is this legacy (to be honest, I never work with support)? If so, make sure your variables are declared as Object
ie:
Dim objConn As Object
Dim objRS as Object
etc
Otherwise the Cypress basic compiler will choke on them when you create the objects. |
|
|
|
Re: External Data in Support Client
Posted: 23 May 06 11:25 PM
|
serevent inhaler reviews serevent inhaler side effects topogroup.com fiogf49gjkf0d It is an Active Form. I have created other active form tabs off of the legacy main form and they work fine. The only problem I have is this ADO connection to another database. I can populate a tab with data from the SalesLogix database. |
|
|
|
Re: External Data in Support Client
Posted: 24 May 06 1:49 AM
|
fiogf49gjkf0d Ignore Application.GetNewConnection. I can't seem to remember this is EXTERNAL data, not internal.
Are you on version 6.2.3 and have both Sales and Support clients on the same machine? You can use SLX Profiler.exe to look at the SQL both clients are generating and compare them. I have a feeling if there is a difference, it's how the SQL is generated into parameters and may or may not be producing the correct result. I don't know of any way outside of the profiler to check for it and if you find that they are in fact different, how do you go about working around it? I'd try matching the SQL as best I could but that may not be enough. It may be something with the coding logic that needs a bug fix from Sage. |
|
|
|
Re: External Data in Support Client
Posted: 24 May 06 1:55 PM
|
over the counter abortion pill cvs over the counter abortion pill walgreens redirect fiogf49gjkf0d So let's get back to the code. What do the strProvider and strSQL variable values look like? |
|
|
|