Timestamp issue

cchappell

I'm trying to connect to an external database. Its a MSSQL 2000 db. The db has over 500 tables. A lot of the tables primary key is a timestamp field. After creating an external link and then looking at the attributes of a business object the time stamp format is yyyy-MM-dd HH:mm:ss.S and I believe that to be correct info.

When I try to do a search on the object I get an error at the status bar at the bottom of the web page. It says "Internal Error Invalid date/time format. If I don't set a primary key then I can do a seach on the object and get results with no error.

Any ideas?

aware_support

Sounds like a bug. We'll investigate and post a message to this thread about the results.

aware_support

This has been fixed in build 946

cchappell

Now that you squashed the bug I'm stumped in how to format a query. I notice that Aware IM formats the time stamp on the screen like so this 2001-01-31 00:00:00.0

Not sure about the exact syntax if I want results from between for example 1999-01-31 00:00:00.0 and 2000-12-01 00:00:00.0

Its kicking my butt...I apologize if this is too EZ.

When I go to create a query the config tools seems to think I am using the wrong format.

Help

aware_support

In queries and in rules please use the following format for timestamp:

dd/MM/yy HH:mm

cchappell

I'm using build 947.

I create a BO named afTrans with Persistence that links to the external db (MSQL 2000 Table) which has time stamps as mention previously in the following format yyyy-MM-dd HH:mm:ss.S

(In Visual Studio it displays the timestamp with slashes instead of dashes that are shown in AwareIm not sure if that has any relevance to the problem.)

I also created a BO named imTrans whose persistence is AwareIM Automatic DB which is using the standard Derby DB.

When creating imTrans one of that attributes is
Trandate = timestamp
I use the same format as the BO named afTrans yyyy-MM-dd HH:mm:ss.S

Because I essentially want to create an awareIM native object that I can dump the MSSQL table to.

I still get the following error in the bottom status pane.

Internal error. Invalid date/time format

Can this problem also be related to the problem below.

aware_support

When do you get this error? When reading afTrans or imTrans? I assume it is afTrans?

The two problems are unlikely to be related but the fact that Visual Studio displays the format with slashes could be the cause of the problem. How is this attribute actually stored in SQL Server - with slashes or with dashes?

cchappell

The type in MSSQL is datetime. Not sure how it is actually stored...

It looks like this 11/11/1998 11:11:11 AM in Vis Studio and another Query tool I used.I'm a newb and not sure how else to peek at whats in the table.

The information below I found on the Usergroup for the Agency Management System that utilizing this MSSQL DB. I snipped it out to see if may shed light...(Could be irrelevant just a guess) Its in reference to someone using Access but I thought maybe Aware IM could be doing something similar.

"date/time criteria for this field in
a query is that the date/time field in AFW is carried out to hundredths
or thousandths of a second. I imagine you are using MS Access. Access
recognizes these sub seconds in the date/time field, (really a double
precision number), but has no date format to display them or to enter
them. "

In reference to your other question.
I can do a "Find ALL" and will pull data from afTrans. Its when I start the process that creates imTrans objects that match the attributes of afTrans. Could the problem be creating awareIM objects that has timestamp format yyyy-MM-dd HH:mm:ss.S

I'm stumped..

Thanks for your assistance

aware_support

Could you please send an e-mail to support@awareim.com?

Thanks

aware_support

Could you try this in the latest build 953? Let us know if the problem is still there.

cchappell

If I click search object and choose afTrans it is still displaying all the records. :lol:

When I go to run the process I am still getting the error but it seems to be more detailed now. 😮

Internal error. Invalid date/time format read from the database as object 9999-01-01 00:00:00.0

I'm assuming that it is thinking 1999 is 9999??

I appreciate your assistance with this problem.

Chris

cchappell

After posting this message I double checked all 400 something fields and found two that said 9999 as the year. :oops:

I changed them to 1999 and it seems to be working now. Thanks for changing the error message! That really helped in discovering the problem! :lol: