INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

Refreshing bound controls

Refreshing bound controls

(OP)
There is a form which is used for maintaining (Creating and editing) records in a table. There are several bound controls on the form. When the form moves to a new record the bound controls show the values from the new record.

When the form moves to a new record, there is an instruction Thisform.refresh(). This works fine if the controls are placed directly on the form.

But if there are two pages on the form (because there are a lot of fields in the table), only the controls on the currently visible page are refreshed - and if you click to view the other page, you see the values from the previous record.

To get round this, after moving to a new record, I am issuing these instructions.

CODE -->

Thisform.refresh()
Thisform.<PageFrame>.Page1.refresh()
Thisform.<PageFrame>.Page2.refresh() 

Is this the correct approach, or are there better ways to do this?

Thanks. Andrew

RE: Refreshing bound controls

With just a few pages, why not?

You can make it a very general approach of doing a refresh within a page.activate event.

Bye, Olaf.

RE: Refreshing bound controls

Andrew,
My philosophy overall is use "REFRESH" methods as limited as possible. Some events will cause a refresh. The default refresh is to update data, but it is also sometimes used to change state (like enabled/disable, visible/not visible, etc). But this can cause "flashing" in your screen. To avoid that a call to "ThisForm.Locscreen = .T." will keep the state of the screen, buand then a "Thisform.LockScreen = .F." will make it active again. There are 2 caveats to consider in that case. 1) If you have other methods that get called that also have "Locscreen" state changes, then they may "unlock" the locked screen, and cause weird visual occurrences. The other is, OLE controls don't "respect" this state either. So if you have OLE objects on your screen, you may need to create other methods and call them explicitly to keep them from flashing during a refresh as well.
It's best to Lock it in once place only, and unlock it in another after complete. This can be challenging.

Best Regards,
Scott
MIET, MASHRAE, CDCP, CDCS, CDCE, CTDC, CTIA, ATS

"Everything should be made as simple as possible, and no simpler."hammer

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close