Change Maybe function

WDSc-i and XP. Java project, local hard drive only.

Tuesday, I open a perspective on the application and change a dozen source
members. Rebuild the whole application, run the tests. Done for the day, but
machines always up and on 1.4 KVA UPS. So, just minimize WDSc.

Wednesday. Restore the minimized window. Open another perspective into the
same application for changing a different dozen sources. Change them,
rebuild. Test, problem, change 6 of the original sources in the other
perspective. Rebuild, everything takes and off with the tests. Minimize
again. Launch the application against live data. Should run for couple of
days.

Thursday. Application stopped, have stack trace. Ok, I see the problem.
Restore the minimized windows. Change the source, hit Ctrl-s, see the popup
and the progress bar. The little asterisk that indicates the source has
changes, disappears. Everything looks normal. Launch the application.

A few hours later the EXACT same error shows up. Like I never changed
source. I look at the source and sure enough, it has Wednesday's date on it.
So I check the source in the WDSc window and it has my changes. So I add
garbage and hit Ctrl-S again. No change on the source date.

Exit reenter, load source and no changes. Change again, hit Ctrl-S and now
it's changed.

Recompile and I'm on my way again.

Did we actually request and get the change maybe function with this product?


===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - iSeries Administrator
 -- IBM Certified Specialist - RPG IV Developer

"There is a crack in everything,
  that's how the light gets in.
    - Leonard Cohen