databaseManager.hasRecords function fails

databaseManager.hasRecords(relationship) fails right after creating a new record which satisfies the relationship. Only when I close the solution and re-open it does the function proceed without issues. Here’s details. Anyone have ideas on how to shake this problem loose?

People stores records of individuals, CR stores call reports,. Each CR record is related to a People record (the person called). A “jump to CR” routine in People first tests whether there are records to jump to with ```
databaseManager.hasRecords(peoid$peo_to_cr)


If a new record in CR is created and linked to a People record, the form draws the new CR, correct ID shown, correct display of the individual's name through a relationship. All appears normal, nothing remarkable. But, if I go to People and use the "jump to CR" routine. the "databaseManager.hasRecords()" test for this individual fails **until the solution is closed and reopened**. Then the test works. No other change than that.

Something appears to be preventing the new record to thoroughly register with the database until the solution is closed. 

A test for the presence of a transaction comes up false. I've inserted a "saveData()" in the new CR creation routine. No effect. I doubt if it should matter, but the new CR routine is within a Form In Dialogue. I'm using the supplied Sybase database.

Any ideas on what could be causing this issue?

Never experienced something like this Morley. What version are you on?

IT2BE:
Never experienced something like this Morley. What version are you on?

Servoy Developer
Version R2 2.2-build 328
Java version 1.5.0_02-b09 (Windows XP)

Morley,

Do you have this also on Java 1.4? I know for a fact that my solution doesn’t work 100% well when working with 1.5 (at least on the client side).

If I am correct 1.5 is not supported at the moment…

IT2BE:
Do you have this also on Java 1.4? I know for a fact that my solution doesn’t work 100% well when working with 1.5 (at least on the client side).

If I am correct 1.5 is not supported at the moment…

Yikes! Thanks. I’ll look into downgrading.