With the release of Windows2008 R2 and the big push for 64 bit desktops/laptops it's time we have an option in the install that would give us 64 bit versions of all the SalesLogix applications.
This does not have to be a "mixed" (32/64 bit) on a given system but should allow us to install either the 64 bit or the 32 bit on a given platform. What would be really nice is that it does an auto-discovery (this should be very easy) if the platform is 32 or 64 bit and "default" to the correct one.
We at my company would also very much like to have 64-bit versions of the software available, especially the OLEDB Provider. We have plans to incorporate SalesLogix into an externally available customer site running on SharePoint, and we were running that SharePoint server on 2008 R2. When we discovered that you can't run a 32-bit and a 64-bit process in the same application pool, we retreated back to the 32-bit world for our SharePoint server.
A 64-bit OLEDB Provider would solve our short-term issues, but full 64-bit versions of the whole SalesLogix application set would be most welcome.
With the release of SharePoint 2010 and the SharePoint 2010 BDCs it would be nice to display some SalesLogix information in a nice SharePoint dashboard, or even create a custom ASP security provider for SharePoint that uses the SalesLogix web access functionality. This would provide customers a SharePoint portal where access can be controled by the SalesLogix users. We currently have such a portal on MOSS 2007, but only in 32 Bit. We would like to move to SharePoint 2010 but cannot because the OLE DB Provider cannot be used.
If you enable 32 Bit Applications on the SharePoint app pool the SharePoint site will not display. This precludes the use of the current 32 Bit OLE DB Provider.
We are facing a great deal of work to move our current enhancements from the windows client to the web client and are taking this opportunity to investigate other options, I.E. MS CRM, Siebel. The lack of a 64 Bit OLE DB Provider from Sage is just one more check in the failure column.
I agree with RJ - come on Sage. You just released SP3 wasn't that the perfect opportunity to release a 64 bit version? Is it really that difficult to recompile your code to work in a 64 bit environment? Anybody from Sage want to comment on a timeframe for implementing this? Seems like low hanging fruit to me and something the community would want and need.
Ted
You are 100% right Ted - this is so way overdue.. at least a 64 bit SalesLogix "Server" implementation. The installer app must be smart enough to install the 32 or 64 bit based on the OS w/zero manual input.
Maybe we could trick them into considering it by asking for an 87-bit version instead, so that when they do the 64-bit version they can say it was their idea.
Just a thought... Seriously, though, the delay on the LAN applications is probably due mostly to Embarcadero still not having a 64-bit Delphi compiler. They're working on it, but the earliest it's likely to appear is late this year, and after that the SLX folks are going to need some time getting it all set up, given all the code and components involved.
I don't believe the OLEDB provider is written in Delphi, I'm pretty sure it's a C++ thingy, but there still might be some porting issues. It would be nice if someone would at least acknowledge that this is becoming a problem.
I was thinking more of a 42 bit version.. like in "...the answer is 42!.." HHGTTU ;-)
Correct on the provider - AFAIK it started as a Delphi C++ item.. not sure if it got made over to a CS C++ (I would hope so).
Had another case come up again where "64" bit install (SQL2008/Server2008R2) turned out not so good... too bad the installation procedure is not 64 bit "sensitive".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We want to hear your cool ideas for enhancing Saleslogix products and services. So add your own ideas or kudo (vote) on the ideas of others here! Watch the most valuable bubble to the top!
I have an idea! How do I get started?
One