Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 5 of 5 total
Thread Two possible bugs
Mon, Apr 6 2009 10:03 AMPermanent Link

Tiago Ameller
If it can not be reproducet, it does not exist. But ...

1. Scheduling jobs in weekly mode doesn't work. I marked all days except sunday. On saturday job was not fired. Otherwiese, dayly schema
works fine. In my country week starts on monday: any chance here?

2. I have two apps on production, two different databases. Never need to repair a table, EDB server is solid!. Ok, but I realized this: Just two new
tables on one database were created all in GUI mode (other were created via SQL script). These to tables have a CBLOB field. One table has two
rows. Saving CBLOB contents in a row erases the other row CBLOB contents. Other table has nine rows. Saving CBLOB contents in row 9 erases
row 4 and vice-versa. This occurs also in my app, not just in manager. After repairing these tables all is working as spected.
Other tables created in script also have CBLOB fields with no problem. Regular BLOB fields are working fine.

Hope this can help!
Mon, Apr 6 2009 5:39 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Tiago,

<< 1. Scheduling jobs in weekly mode doesn't work. I marked all days except
sunday. On saturday job was not fired. Otherwiese, dayly schema works fine.
In my country week starts on monday: any chance here? >>

I'll check it out.

<< 2. I have two apps on production, two different databases. Never need to
repair a table, EDB server is solid!. Ok, but I realized this: Just two new
tables on one database were created all in GUI mode (other were created via
SQL script). These to tables have a CBLOB field. One table has two rows.
Saving CBLOB contents in a row erases the other row CBLOB contents. Other
table has nine rows. Saving CBLOB contents in row 9 erases row 4 and
vice-versa. This occurs also in my app, not just in manager. After repairing
these tables all is working as spected. Other tables created in script also
have CBLOB fields with no problem. Regular BLOB fields are working fine. >>

This has already been fixed for Build 11 in response to the incident report
that you submitted on March 19th.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mon, Apr 6 2009 9:35 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Tiago,

<< 1. Scheduling jobs in weekly mode doesn't work. I marked all days except
sunday. On saturday job was not fired. Otherwiese, dayly schema works fine.
In my country week starts on monday: any chance here? >>

I looked into this, and found the issue.  The scheduling is using an
incorrect second check on the number of days since the last run, and that is
messing up the weekly day scheduling.

A fix will be in Build 11.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Apr 7 2009 2:25 AMPermanent Link

Tiago Ameller
Tim,

<This has already been fixed for Build 11 in response to the incident report
that you submitted on March 19th.>

Ok, in that incident report I submit very few information of how reproduce it. When I had a reproduce way I posted it again. Sincerely, three
weeks is a lot of time for my 2 kb RAM in my head SmileyI just forgot it.

I know your are a *lot* of bussy with we EDB/DBISAM users posting all day, but it would be great to have incident reports facility updated in order
to know the state of issues. Thanks Tim for your heavy work!
Tue, Apr 7 2009 6:50 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Tiago,

<< Ok, in that incident report I submit very few information of how
reproduce it. When I had a reproduce way I posted it again. Sincerely, three
weeks is a lot of time for my 2 kb RAM in my head SmileyI just forgot it. >>

No problem - just letting you know that it's the same issue. Smiley

<< I know your are a *lot* of bussy with we EDB/DBISAM users posting all
day, but it would be great to have incident reports facility updated in
order to know the state of issues. Thanks Tim for your heavy work!  >>

I know, I need to be more proactive about updating the incident reports in
real time.  I should also probably be stricter about enforcing the need to
submit an incident report.  That would allow me to have them published in
real-time, similar to Mantis or other types of online bug-tracking systems.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image