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!

External Development Forums - SalesLogix OLEDB Provider
Forum to discuss using the SalesLogix OLE DB Provider from external applications (including usage of built-in provider procedures). View the code of conduct for posting guidelines.

Forums RSS Feed

Back to Forum List | Back to SalesLogix OLEDB Provider | New Thread

View: Search:

Author

Thread: Datetime and GMT Issue

John Gundrum
Posts: 632

Datetime and GMT Issue Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 06 Mar 09 8:30 AM

I created a view in the SalesLogix database for Opportunities. The view includes the estimatedclose field - a datetime field. The problem is that when I use the view to create an Opportunity group, the estimatedclose datetime field is NOT reflecting the correct date. For example, if an opportunity has an estimated close of 4/1/2009 the list view shows the date as 3/31/2009. I know this has to do with the SLX OLEDB provider not calculating the stored date value (GMT 0) to the time zone on my computer (GMT -5). Two questions

Why is the provider not doing the conversion for a view?

I need the date field shown to be accurate. How do I modify the view to calculate the estimated datetime field to the local machines time zone? There will be PCs in different time zones so the calculation in the view has to be dynamic based on the local PCs time zone.

Thanks,
John G.

[Reply][Quote]

RJ Samp
Posts: 973

Re: Datetime and GMT Issue Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 18 Mar 09 8:50 AM

SLX OleDBProvider resolves timezone data in a VIEW? didn't/don't know that.

Opportunity.EstimatedClose is a DateTime DataType per the SecTableDefs entry? Ours is a 'D', DateOnly field. I've never worried about the TIME that a deal was going to close, only the Date.

So you are storing 4/1/2009 00:00:00 in an SLX ONLY THROUGH OLE DB PROVIDER datetime field.....SLX leaves it alone at 4/1/2009 and the rest of the SQL world provides your regional settings offset to Midnight and makes it yesterday.....

Understand that completely......

What happens if you store Opportunity.EstimatedClose at DATEVALUE(Opportunity.EstimatedClose) & " 23:59:05 " kinds of stuff.....I'll bet you don't have the issue.

[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 \|

page cache (param): 5/15/2024 5:48:08 AM