No, the 9.1 ArcSDE SDK dlls are not sufficient to connect to 9.2 with the 9.2 plugin. The plugins are linked against each specific version of the ArcSDE SDK and have to be matched. The use of plugins makes this less obnoxious than it was in the past, which required swapping out the entire libmap.dll, but it is still some hassle.

The rules for ArcSDE MapServer connections are as follows:
- If you have to connect to both ArcSDE X.1 and X.2 servers, use the X.2 version of the ArcSDE SDK. You can usually connect to a X.1 version server with X.2 version client DLLs without ill effect. - To connect to X.2 servers, you *have* to use X.2 versions of the ArcSDE SDK. - Do not use both the X.1 and X.2 versions of the plugins in the same MapServer map if you have to connect to both X.1 and X.2 version servers. Just use X.2.

Howard

On Sep 11, 2007, at 10:21 AM, Josh Hevenor wrote:

I had a quick question on using the msplugin_sde_92.dll to connect to an SDE service from mapserver. The SDE Notes from the README file state the following: As of Map Server 5.0 (including betas and release candidates), the following applies:

Steps to Enable SDE 9.1 and 9.2 Support in MS4W's Map Server

***********************************************************

1. Make sure the ArcSDE? SDK dlls for 9.1 are available on… But it doesn’t mention arcSDE 9.2 SDK dll’s for connecting to a 9.2 service. Are the 9.1 dll’s sufficient? I’m just working through my setup and thought I should clear this up as I go along. Thanks,


Josh Hevenor
Application Developer
____________________________________________
5230 South Service Road
Burlington, Ontario
L7L 5K2  Canada
Phone: 905-333-4544 ext. 19
Fax: 905-333-0455
Cell: 905-320-7525
Email: [EMAIL PROTECTED]
Internet: http://www.dpra.com
<image001.jpg>






Attention:
Privileged/Confidential Information may be contained in this message. Disclosure to any person other than the named recipient is unauthorized. If you are not the intended recipient, please delete all copies of this information and kindly notify the sender by reply email. Opinions, conclusions and other information in this message that do not relate to the official business of DPRA shall be understood as neither given nor endorsed by it. DPRA and any of its subsidiaries reserve the right to monitor all e-mail communications through its networks. Thank you.




Reply via email to