>Question 1: I guess I am not really sure how the dataenvironment plays into things. In some cases I can use tables without putting them in the datenvironment and other times I need to. Should I only put tables in the environment when I NEED them on the load of the page and then find some other way to open them when I need them?

I think that opening a table (DBF) should be no problem, no matter how big. The potential problem is with a big view, if it has many records, or - even with few records - if it is not properly optimized.

>Question 2: Are there any ways to optimize the OPEN of the table? I am not even trying to select against the table yet. It is almost like the entire table is pulled accross the network as soon as it is opened.

See above. To opotimize the opening of a VIEW, most of the suggestions for optimizing queries ( see FAQ #8109 ) should apply.

>Question 3: Since it appears that table opens are the main thing that is slowing me down, would it help at all to use an appliction loader? If I do, would it require significant changes? One of the benefits of running the application over a shared folder is that it only need to be updated in one place. Another is that installing it on other PC's is as easy as creating a desktop shortcut to an .exe over a mapped drive.

If the startup time is no problem, as you state, I would leave things as they are. I don't believe having the executable on the local machine has a significant impact after the application is loaded.