In the current incarnation of our application, each menu choice calls a program which opens the needed tables, does any setup work, then runs the form, then closes the tables when the form is done. This was necessary because the table name wasn't a constant with each form. Rather, it was a three letter code of the current operation plus the standard table name.

I'm conpletely redoing the program for the next version and have decided on what I think is a more sensible approach. Im going to give the tables all standard names and just have a different directory for each operation.

From experimenting with the form wizard, I discovered you can tie the table to the form directly and it will take care of opening it for you. I'd like to use this approach and eliminate the calling programs. But I have a couple questions:

If I run a form from a form and they use the same table, will there be a conflict when the second form loads? Or does it know the table is open already and not try to open it again?

One of the data environment properties has the path to the table hardcoded in it. I don't want that; I want it to look for the table in whatever is the current directory. But it won't let me edit this property. How do I fix that?

Thanks,