> >I have three databases that collect and process information. One generates
> > cost center usage percentages that are used in the other two. One of those
[quoted text clipped - 12 lines]
>
> Keith.
> linking tables will only complicate the intentional separation of the
> databases,
So you want to process data from more than one file yet keep them all
separate? Not gonna happen without linked tables. What complication would
it cause?
> and would not suffice since the tables undergo much query
> processing
The performance hit on linked tables in my experience is negligible provided
that the FE is on the user's local drive.
> and are managed and handled through forms. It would be useful if I
> could link to the forms in the other tables, but I don't know if that can
> be
> done. I mean, I don't know how I would do that programmatically from the
> "external" database.
To the best of my knowledge you can't call a form in one database from
another, but then why would you want to? I don't see any problem with
linking tables and using native forms in this type of scenario.
Keith.
Ray S. - 02 Mar 2007 12:41 GMT
OK, then I guess I have no alternative. I thought I could programmatically
open an external database and use it's objects. As it is, each database has
its own main form that does it's thing. However, they are all related in that
one database creates and transfers a table into the other two that is crucial
for their processing. I was hoping to provide one source from which to run
the processes for all three in the proper sequence.
> > linking tables will only complicate the intentional separation of the
> > databases,
[quoted text clipped - 20 lines]
>
> Keith.