Skip 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.

Error 106: Table is missing

Featured Replies

Hi all,

Need some help on an error that I'm seeing OCCASSIONALLY.

Several scripts in the system I've developed are used to create new records (rather than allowing creation through portals, etc.). Usually (although not in every case), I pop a very tiny window for the new record to be created in (go to the right layout/table) and then perform the new record step. I've put a trap in for the occurence of an error because a few times a day the new record step is failing. The trap has let me know that the error I'm actually getting is #106 -- Table is missing. Happens in different tables/scripts throughout the day.

Any thoughts on why this would happen intermittently would be helpful.

Much appreciated,

Kate

It would be helpful if you could post your exact script so we could see what might be causing the problem.

  • Author

Thanks for your reply.

The full script is quite lengthy with several different parameters, etc. but here's the very beginning of it with a section that fails every once in a while.

Set Error Capture [ On ]

If [ Get(ScriptParameter) = "Add Job" ]

Set Variable [ $OrderID; Value:ORD__~tog::__pk_OrderID ]

Commit Records/Requests

[ No dialog ]

New Window [ Name: 1; Height: 0; Width: 0; Top: -20; Left: 0 ]

Go to Layout [ “JOB.job.utl” (JOB__~tog) ]

New Record/Request

Set Variable [ $Error; Value:Get(LastError) ]

If [ $Error ≠ 0 ]

Show Custom Dialog [ Title: "Yikes!"; Message: "PROCESS FAIL: Please notify Kate ASAP that you've received message: "&

$Error&". Thanks!"; Buttons: “OK” ]

Close Window [ Name: 1; Current file ]

Exit Script [ ]

End If

Set Field [ JOB__~tog:;)_fk_OrderID; $OrderID ]

Commit Records/Requests

Close Window [ Name: 1; Current file ]

Go to Layout [ original layout ]

Go to Field [ ord_UI~all::ActiveTabOne ]

Go to Portal Row

[ Last ]

Go to Field [ ord_JOB~orderIDnocreation::JobDescription ]

You'll note the If statement that I have in there that I'm using to capture the error code. So far, 106 is what my users report seeing when they receive the message.

BTW, I'm using the separation model -- data in one file and interface (scripts, layouts in another). We're running on a brand new dedicated server with 2g of RAM and 7200 hard drive.

Thanks for any insight.

Kate

Everything looks fine. I'm not sure what to say, especially since the problem is intermittent. The only thing I can think that would block the creation of a record is security. It could be possible it is your version of FileMaker. You might want to try updating to the most current revision which is free from the filemaker.com web site. Other than that, you need to figure out under what circumstances the problem occurs. In other words, you need to to reproduce it whenever you want. In this way, you will figure out what is causing the problem.

Create an account or sign in to comment

Important Information

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

Account

Navigation

Search

Search

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.