View User Profile

Comment: Re: Creating SalesLogix Table ID Values - The Definitive Guide fiogf49gjkf0d Hi John - thanks for your help. As it turns out, the server does already have the SQL Native Client installed, so it looks like I'll need to keep digging. It does look to me like my problem is related to this existing forum thread, http://www.slxdeveloper.com/forum.aspx?forumid=3000&postid=11604 so I will need to work through the solutions offered there and see if one of those helps. Thanks, Matt Author: Matt Boerger - 5/29/2009
Comment: Re: Creating SalesLogix Table ID Values - The Definitive Guide fiogf49gjkf0d Looking back over that last post, I think I got myself a little tangled up, and had better clarify. Using test.udl, I was successfully able to connect to the database from our app server using both the Native Client, and the SLX Ole DB Provider, but it was the Provider connection string that I have tried to use in my application. I'm taking it that the Native Client connection string, which uses the sysdba credentials, would not be appropriate for use in the application. Author: Matt Boerger - 5/29/2009
Comment: Re: Creating SalesLogix Table ID Values - The Definitive Guide fiogf49gjkf0d Hi John - thanks for the response. Sorry to be such a newb, but which server are you referring to, the application server for our external application, or the SalesLogix server where our database and SLX services reside? I checked in SQL Configuration Manager on the SalesLogix server, and there is a Native Client configuration item there, which appears to me to indicate that it is installed. There is no Native Client service showing up as a service on either machine, but I don't know that there would be. I used the test.udl to test creating a Native Client connection from the application server, and that connection succeeded - but when I use the connection string from the udl file in the application, it still gives me the 'unable to initiate the data dictionary' error. Two other notes, for what they are worth. First, the new connection string works fine for me in the development instance of the application on my XP machine. It only has problems on the Windows Server 2003 production server. Second, the pre-upgrade application's connection string pointed to an instance of the Provider running as a service on the application server itself, but when I changed the connection string to the new format for 7.2.2, I pointed the connection directly to the database server - which as I already mentioned - works fine with test.udl, just not in the application. Anyhow, I know this is pretty far off topic for this article, but at this point any advice anyone can provide that will let me get this application back up and running would be greatly appreciated. Thanks, Matt Author: Matt Boerger - 5/29/2009
Comment: Re: Creating SalesLogix Table ID Values - The Definitive Guide fiogf49gjkf0d Phil - thanks for your reply. You have, of course, hit upon my big mistake. This insert is from a legacy external app that I have inherited. Since our upgrade from 6.01, I have been unable to get the Provider code to work on our production application server (I get a 'Unable to initialize data dictionary.' error). This insert into OPPORTUNITY was the only thing that the application needed the provider for, and after reading about the auto-increment option here, I mistakenly believed it would allow me to forego the Provider connection and perform the insert directly through SQL. After searching around for more information on the auto-increment capability, I eventually realized that it doesn't allow you to bypass the Provider, so it looks like I am back to having to figure out what the Provider is choking on in our server environment. Good to know about the physical PKs. I will ask about that. Notably, our integrator inherited this installation from a previous vendor, too, so the upgrade has - for better or worse - been a bit of a learning process for all of us. Author: Matt Boerger - 5/28/2009
Comment: Re: Creating SalesLogix Table ID Values - The Definitive Guide fiogf49gjkf0d Great article -- very helpful. However, I am not having any success trying to use the autoincrement feature. I have tried to turn on autoincrement for opportunity as described by Ryan, but after setting AUTOINCREMENT to 'T' for OPPORTUNITYID, I am still getting a "Cannot insert the value NULL into column 'OPPORTUNITYID'" error from this insert statement. `INSERT INTO sysdba.OPPORTUNITY (ACCOUNTID, SECCODEID, DESCRIPTION, CLOSEPROBABILITY, STATUS, SALESPOTENTIAL, AccountManagerID, LeadSourceID, CreateDate) VALUES (@ACCOUNTID ,'SYST00000001', @DESCRIPTION, '10', 'Open', '0', @ACCTMGRID, @LEADSRCID, getDate());` Ryan mentions that autoincrement only works for key columns, but I took that to mean conceptual keys, since - in my SQL2005 database at least - there are no PKs on any of the tables. I also do not see the 'Key' checkbox in DB Manager for any table. I did check and OPPORTUNITYID does not have KEYFLAG set, but neither does ACCOUNTID (from Ryan's example), or any other field in the entire SECTABLEDEFS table. Is KEYFLAG the issue, and if so can I change the value myself? Would setting the flag direcltly in SECTABLEDEFS be sufficient, or would I need somehow effect the change through DB Manager to make it take effect. We are running 7.22 - recently upgraded from 6.01 by our integrator. I am working in Architect as admin. Author: Matt Boerger - 5/27/2009

slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation. This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.	code of conduct \|

page cache (param): 11/23/2024 11:23:33 PM