>>>>>>Please see my message to Garrett Fitzgerald regarding the reasoning. If
>>>>>Microsoft has the addobject command available for the data environment, there must be a way to make it work. . .
>>>>>>
>>>>>
>>>>>I'm reading it now.
>>>>>Remember some consider the DataEnvironment to be a crutch. It is not necessary. Any thing you can do in the DataEnvironment can be done programatically.
>>>>>
>>>>>BTW, do all of those 100 files have the same structure?
>>>>>
>>>>>>JR
>>>>
>>>>Really? I was under the impression that only files in the DataEnvironment would handle table- & row-buffering.
>>>
>>>>
>>>>The 100 name files have the same structure, but the files which they will be manipulating have different structures.
>>>
>>>No you can set up buffering manually as well as through the DE.
>>>
>>>You could using an alias. Add the table to the DE and then when you select table just alias it always with the same name of the table you added to the DE.
>>>I'm sorry, I didn't spend enough time reading through your message to Garrett whether this is a possible solution or not.
>>
>>The problem is that it's not actually using the file when it's added to the environment. ie:
>>
>>Thisform.Dataenvironment.Addobject([Cli_name],[Cursor])
>>Thisform.Dataenvironment.Cli_name.Buffermodeoverride =2
>>SELECT Cli_name
>>
>>will return an "Alias does not exist" or whatever--it's not in use.
>>
>>JR
>
>I mean open the DE at design time. Add the table to the DE. Now whenever one of these tables is opened just make sure it has the same alias and be sure you have autoopentables set to .t. .

Interesting. So I just fake it out by giving it an alias. But what about the orig. table? I'll have to close it to be sure I'm not updating the wrong table.

JR