Re: merge multiple databases

From: Jim Carlock (anonymous_at_127.0.0.1)
Date: 05/14/04 

Date: Fri, 14 May 2004 15:35:22 -0400

I think there are other things that might play into it as well.
When I did it, it was through an ODBC connection, and
maybe I just fell into the fact that the Internal Access query
was faster, and perhaps it was just easier to read for me.

There were a few thrings I tried but I don't remember
exactly if that specifically was one of them. I ended up
with an internal Access Make Table query and then a
ton of update queries. The biggest problem I had was
getting the download of the initial tables and I had tried
doing selective queries but that ended up taking over 24
hours, I tried VB SQL and decided that using the Access
queries was much better for some reason. I left some
VB string SQL in place for delivering the data to the
report generator, as there were 1000s of accounts and
some some accounts with 1000s of transactions that
needed printing.

I'm kind of hoping DIOS tries it out and gives a Yay or
Nay. 

-- 
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.
"YYZ" wrote:
"Jim Carlock" wrote:
> If you put the SQL into queries inside of Access, I'm thinking that
> it should get even faster... IE make the query in the new Access file,
> and then call that query from the VB application, with an .Execute
> if it's an action query, or with the .RecordSet object if it's a Select
> query.
>
> If the query inside of Access was named "qSelectAllRecords", then
> you can open it with :
>
> Set rs = gDAO_DB.OpenRecordset("qSelectAllRecords")
I've done some half assed testing with that in the past, and never really
noticed a difference.  But again, it was half assed, so you may be right.
Matt

Relevant Pages

  • Re: Official Status of SQLServer 2005 ADP
    ... I have said that the support for SQL passthrough ... queries under MDB was bad and worst than the one offered by ADP while you ... > attempt to "pass through" every Access query against a linked ODBC ...
    (microsoft.public.access.adp.sqlserver)
  • Re: "Query Too Complex" Errors
    ... few dozens of queries, in the middle of which there's a long chain of ... we've been having a lot of those "Query Too ... some of the complexity in the SQL ... SQL statement you are working on. ...
    (microsoft.public.access.forms)
  • Re: Dynamic query problem
    ... On Oct 17, 9:41 am, Andy Hull ... If we were to provide a fully featured dynamic query generator we would have ... Provided with already built queries which they can edit ... SQL and see where it is the same as for the other queries and where it ...
    (microsoft.public.access.queries)
  • Re: CONTAINS performance
    ... mark, FTS needs to be very carefully tuned to achieve second response times, ... see SQL Server 2000 BOL title "Full-text Search Recommendations" for more ... When you include the "TOP 100" in your query, you are in fact limiting the ... valid for SQL queries, they often do not apply to FTS queries because the FT ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Populating a list -- learning Access
    ... It is kinda funny -- I started using databases in the early 80's with dBase and, for years, never knew that I knew SQL! ... If you are on a form or report, the most important property is the NAME, because that is how you refer to it in code. ... I don't mean to skip your responce below, but thanks to your help with SQL, I was able to get the query to pull the info the way I needed. ... Queries (just shows the QBE grid for convenience -- ...
    (microsoft.public.access.forms)