I've run into a problem that I've never seen before. The bulk of the data in a particular view comes from one Access database, but one field may be wanted from a related table in a totally different Access database. I have zero control over the first database, and little control over the second. Frankly, I can see three ways to go, but I'm looking for a better way than any of them. The three ways are these:
1) The number of records is trivial, so create a datatable from the first database, then add a column and query the second database for the information for that column record by record. This appears to be the way the legacy program worked....sort of, except that it didn't do this well, so I'd want to do it better.
2) Create a datatable containing the information from the first DB, then create a datatable containing the information from the second DB, then join the two using LINQ, and display.
3) Declare the whole thing silly and move on. After all, there is no reason that I can see to have the information from the second database, and since the legacy program wasn't working right anyways, it may be that nobody would care if I left it out.
The only argument against #3 is that I hate to leave it at that. I'd rather go with option #2, but I was hoping there might be a way to make a JOIN across two different databases. This can be done in SQL Server, but I don't know about Access. Any ideas?