Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Managing Data Entry

Featured Replies

This might seem like a silly question, but I'm pretty new to filemaker.

In the database that I am creating, users can only add records through the 'Add Record' layouts that I made. I was concerned with people canceling part-way through and leaving garbage in the database, so the fields in the 'Add Record' layout are globals that are set to the actual table when they click on the 'Add' button. Is this the best way to do this? If so, should I have a set of globals for each table where users need to add records (gName, gPart_Number), or a set of globals that are used for all 'Add' layouts in all tables (gAdd_Temp1, gAdd_Temp2)?

Thanks

  • Author

No suggestions?

Why not use the built-in Commit/Revert process?

See also:

http://fmforums.com/forum/topic/66874-commit-or-rollback/page__p__317187#entry317187

  • Author

I'm not using Commit/Revert because writing the data to the record after everything is complete and validated seemed 'cleaner'. But, like I said, I'm just starting out with FM. How do you avoid garbage data when users close the window or the program crashes with this method?

You will get a prompt to save the record when you attempt to close the window. I don't know about crashes, but I would assume an uncommitted record would not be saved.

---

I should add that entering data into an uncommitted record is NOT the same as "writing the data to the record". That only happens upon commit.

Edited by comment

One of the BIG problems I have repeatedly seen with systems that force data entry into global fields is that unless the process is "completed" the data is lost. Users then complain of lost records and the confidence in the system quickly deteriorates.

I'd rather suffer a couple of incomplete records (which are easy to delete) than create a system that can cause data loss.

Are you implementing the global data entry fields to solve an actual problem? Or does it just seem like a Good Idea . :D

Edited by Vaughan

  • 4 weeks later...
  • Author

It seemed like a good idea. I went through and changed everything as you guys suggested. Thanks.

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.