IMO, the status bar is interactively sensing what's happening as your application is running specifically on table manipulations. These behaviour sometimes is beyond our control. I would rather suggest to make use of ActiveX Status bar.
>In my application executable, I keep the status bar on (mainly because early on I noticed some quirky behavior -- can't recall what, though -- when it was kept off). Though I keep TALK, NOTIFY, etc. set OFF, in some places I get undesired status messages, usually (maybe exclusively) info on the currently selected table, e.g. "Record: 1/1 Record Unlocked". I really can't see any reason this should happen, but when and where it does, it's consistent. I could also swear, in some cases, that I've seen such messages on clients' computers, where they DON'T appear on my machine, running the exact same executable.
>
>I thought I had this all figured out once, but I guess not. Can anyone enlighten me?
JESS S. BANAGA
Project Leader - SDD division
...shifting from VFP to C#.Net
CHARISMA simply means: "Be more concerned about making others feel good about themselves than you are in making them feel good about you."