View Full Version : Database Explorer - Table not open

Tom Murphy
30-Apr-2017, 11:00 PM


After playing around with the columns I am now getting table not open errors -


In settings, 'Open All Related-to Tables' and 'Open All Related-from Tables' are not checked, and 'Display All Errors' is checked.

Vincent Oorsprong
1-May-2017, 06:07 AM

Like to learn more from you about how to reproduce the error. Currently I can't duplicate.

Tom Murphy
2-May-2017, 01:13 AM
Hi Vincent

Go into dbExplorer and open the Order Entry workspace.

1. expand 'Order Detail' in the tree view
2. expand the Columns
3. click on all the columns except 'Item_ID'


4. then right click and 'Rebuild Dataview'
5. click on the 'Order Header' table
6. click back the on 'Order Detail' table

and you should see the error...

D:\Program Files (x86)\DataFlex 19.0\Bin\dbExplor.exe
Table not open Tablenumber = 0, Source = API.Get_Attribute

Error: 72

MSG_ERROR_REPORT (433) - oErrorDialog (91) - at address 67317
MSG_DOCREATEDATAGRID (11400) - oDataTabpage (1237) - at address 92728
MSG_DOCREATEINITIALDATAVIEW (11553) - oFileDataTabDialog (1178) - at address 98018
MSG_DOCREATEDATAFILEVIEW (10641) - oMainpanel (64) - at address 71554
MSG_DOREQUESTOPENFILE (11065) - oFilelistTreeView (770) - at address 83907
MSG_ONTVFILETIMER (10918) - oFilelistTreeView (770) - at address 83886
MSG_ONITEMCHANGED (6337) - oFilelistTreeView (770) - at address 84065
MSG_NOTIFY (723) - oFilelistTreeView (770) - at address 24635
[start] - at address 101455

Vincent Oorsprong
5-May-2017, 02:41 AM

Followed your instructions but can't get the error appear. Maybe you can make a small video recording showing the problem?

Samuel Pizarro
5-May-2017, 08:28 PM
I could not reproduce it either!

Clive Richmond
7-May-2017, 03:34 AM
Hi Samuel,

I could not reproduce it either!

Check 'Open All Related-to Tables' configuration option and see if that'll break for you.

Vincent Oorsprong
7-May-2017, 08:25 AM

Thanks. This brought two flaws in the picture but I still don't see the error 72 reported by your colleague Tom. This were fixes for "bad table number".