Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Wednesday, May 1, 2024 
 slxdeveloper.com
 Community
 Members
 General
 Architect
 External
 Web
 Downloads
 Resources
5/1/2024 5:29:58 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!
 Data & Imports Forums - T-SQL & Queries
Forum to discuss general T-SQL questions and help with queries related to SalesLogix data. View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to T-SQL & Queries | New ThreadView:  Search:  
 Author  Thread: Query won't work through provider
Marc Johnson
Posts: 252
 
Query won't work through providerYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 14 Nov 06 10:27 AM
fiogf49gjkf0d
I'm trying to run the following query with no luck.
--------------------
SELECT sysdba.Account.Account, sysdba.Account.InternalAccountNo, sysdba.Oracle_Address.Customer_Name, sysdba.Oracle_Address.Customer_Numer

From sysdba.Account INNER JOIN sysdba.Oracle_Address
ON sysdba.Account.InternalAccountNo = sysdba.Oracle_Address.Customer_Numer
--------------------

I've used Query Express and ADO Explorer, both going through the SLX provider. If I go directly to Oracle or MS SQL it runs fine.

The Oracle_Address table was NOT created with the Database Manager. This was done by the DBA because the table is just a 'holding table' and SalesLogix wouldn't be accessing this table within the client app. We are going to write a script that will compare addresses from our primary customer DB (Oracle Apps) against what is in SLX and update SLX if needed.

Is the provider throwing up because the Oracle_Address table is not a valid SalesLogix table? Is there a way to hack the table now that it's created to make it 'valid'?
[Reply][Quote]
Frank Chaffin
Posts: 475
 
Re: Query won't work through providerYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 14 Nov 06 11:33 AM
fiogf49gjkf0d
What is the error you are getting?

Does sysdba own the Oracle_Address table?

BTW, you should not need the SYSDBA prefix when you go through the provider. This is because the provider connects as sysdba.
[Reply][Quote]
Marc Johnson
Posts: 252
 
Re: Query won't work through providerYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 14 Nov 06 11:51 AM
fiogf49gjkf0d
Removing the 'sysdba.' prefix and it worked. I'm sure i've been using sysdba. on other simple selects (no joins).
[Reply][Quote]
Frank Chaffin
Posts: 475
 
Re: Query won't work through providerYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 14 Nov 06 11:59 AM
fiogf49gjkf0d
Great. Feels like the provider was getting confused by the syntax.

Were you getting table does not exist error?
[Reply][Quote]
Marc Johnson
Posts: 252
 
Re: Query won't work through providerYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 14 Nov 06 12:01 PM
fiogf49gjkf0d
No, it was stating that it could not parse the SQL.
[Reply][Quote]
Frank Chaffin
Posts: 475
 
Re: Query won't work through providerYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 14 Nov 06 1:17 PM
fiogf49gjkf0d
I just did some experimenting on one on a local databases and was able to reproduce the failed to parse SQL error.
[Reply][Quote]
 Page 1 of 1 
  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!
 

 
 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 | Subscribe to the slxdeveloper.com Latest Article RSS feed   
 
page cache (param): 5/1/2024 5:38:07 PM