Search Form Across multiple Access and SQL databases

Hello,


In this question I'm looking for some conceptual guidance rather than specific help.

I am creating an Access front end to make it easier for users to view or write information from a couple of different databases.  Some of them are Access based on a network drive and a couple are on a SQL Server.  

I am hoping to start the users out on a SEARCH FORM where they can get to the RESULTS FORM by typing in any number of limiters.  I wrote a quick loop through the text boxes to create the sql statement which works fine on a single database.  Since I have multiple databases would it be fair to do the same for each database and add the matching records to a recordset and then display that recordset in the unbound RESULTS FORM? The user would choose by clicking on the row of which address they want to look and be sent over to the DETAILS FORM that uses subforms for each database based on the street address.


The nearest thing to a common key among the databases is a street address of the property.  Since the addresses may be keyed differently across db's it may be difficult.

Or is there some other way people have found to consolidate several db's onto a single tabbed form with subforms?

I inlcuded a picture of the basic layout so far.
Search.jpg
zipnoticAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dqmqCommented:
My suggestion is to create a local table using a make table query against the first database you are searching.  Then run an append query to the same table against the subsequent databases that you are searching.   After all queries are completed the local table then contains the collective "matches".   The results form can be bound to the local table.

The local table would probably need to include a column or two that identifies the source system/database/table where the row originated.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
zipnoticAuthor Commented:
Is there an advantage to creating a local temp table and appending to it rather than creating a recordset in memory and appending to that then displaying the RESULTS FORM ?
dqmqCommented:
Two, I can think of:

1. It's a lot simpler.   For example, the append to a table is one set-oriented statement.  The append to a recordset is a procedural loop on the order of 10 statements minimum.  The unbound RESULTS form is similarly an order of magnitude more complex than one that is simply bound to a temp table.

2.  Using persistent storage means the search results survive an Access shutdown--allow you to resume where you left off, so to speak.
zipnoticAuthor Commented:
Much appreciated.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.