TdaMetaData:GetFieldsFromDataSet

rbuser

Hi,

Several of my customers still get the TdaMetaData:GetFieldsFromDataSet error
on some pcs. I never found the problem. I really do not understand what's
wrong. My program is developped with Delphi 7 and RB 9.02 and access a
Firebird 1.5 database using dbExpress.

Here are some new questions:

My database structure never change and reports are using DataDictionary. The
only difference between databases is that in some databases, descriptions in
the field alias in the table RB_FIELD can be in French or in English. Same
thing for the description of Table Alias in the table RB_TABLE. Only
description can be different. Fields have always the same name (It is the
exactly same database structure). The only difference is the connection
string since the database file can have any name and can be located in
different folder but there is no problem there since I'm using a
TSQLConnection and everything works fine for 99% of my customers. Vustomers
who get problems get this problem only on some pcs and not on all pcs.

Question #1)
According to my configuration explained abov, Is calling
gMetaDataManager.Clear can help me or it will not change anything?

Question #2)
Is the meta data cache is created each time my program run ? If not, were
this meta cahe is kept exactly ?

Thanks.
.
G. Plante

nardmoseley

- Make sure that DataDictionary.UseTableOwner is set to False.

- The meta data cache is a memory based cached - it built each time the
application runs. It is not stored to disk.

- Clearing the meta data cache is only helpful if you are trying to switch
to a different database or add tables, etc while the application is running.


--
Nard Moseley
Digital Metaphors
www.digital-metaphors.com

rbuser

Hi,

Just to let you know that I finally found the problem. It was because
dbExpress was not able to find the fille midas.dll. What's strange is that
the error message never indicated that it was because this file was not
found. The file midas.dll was registered as being located in a wrong
directory. So, registering it again using regsvr32.exe fix it.

G. Plante

nardmoseley

Glad to hear you solved that mystery.

Thanks for providing that information. Very helpful for other customers
using Midas.