I'm trying to use a memory TDBISAMTable and I've set the databasename to
 MEMORY. I've added several fields to the fields editor and tried to
set the table active at design time and I get an exception "You must
define at least one field before you can open an in-memory table at
design-time". Well, I've defined 4 fields and still can't open it.

I have the table's SessionName set to the same session as the other
tables. Should memory tables have a new session table?

Other times when I try and open it at design time I'll get "DBISAM
Engine error # 11010 Table of backup file 'mymemorytable' does not exist".

Is there a trick to using a memory TDBISAMTable?? I couldn't find any
references to using a memory table (except SQL) in the help file. Does
anyone know what the help topic is?

TIA

Dave
DBISAM v4.22

Dave Harrison wrote:

> I'm trying to use a memory TDBISAMTable and I've set the databasename to
>  MEMORY. I've added several fields to the fields editor and tried to set
> the table active at design time and I get an exception "You must define
> at least one field before you can open an in-memory table at
> design-time". Well, I've defined 4 fields and still can't open it.
>
> I have the table's SessionName set to the same session as the other
> tables. Should memory tables have a new session table?
>
> Other times when I try and open it at design time I'll get "DBISAM
> Engine error # 11010 Table of backup file 'mymemorytable' does not exist".
>
> Is there a trick to using a memory TDBISAMTable?? I couldn't find any
> references to using a memory table (except SQL) in the help file. Does
> anyone know what the help topic is?
>
> TIA
>
> Dave
> DBISAM v4.22

Ok, I learned something today. I entered the fields using the
FieldDefs property in the ObjectInspector and then I could open the
memory table. I always thought using the FieldsEditor would be the same
as adding fields to the memory table definition. D'uh?

Dave

Dave,

<< Ok, I learned something today. I entered the fields using the
FieldDefs property in the ObjectInspector and then I could open the memory
table. I always thought using the FieldsEditor would be the same as adding
fields to the memory table definition. D'uh? >>

Unfortunately, no. The FieldDefs define the structure whereas the TFields
surface the ability to read/write to the fields and define virtual fields.

--
Tim Young
Elevate Software
www.elevatesoft.com