ODBC Connection

[whartman]

I setup an ODBC connection and then used a word docs to complete some documents.

Our individual list has about 800 entries and it takes about 50 secs to load (I clocked it).

Versus our gift tax list is about 15 entries and is pretty instant.

I assume the speed is a slow since it is loading all the data from that module.

Is there a way to speed this up?

Thanks

[DatabaseRobert]

Is the delay in the creation of the merged document, or in the loading/opening of the Data1-Client Info file in the first place?  (I suspect the first.)

If the slow-down is in the creation of the merged document, you may be able to set it up as a query (or limitation, range restriction, or some other terminology unique to Word) such that you are only processing <these 16 clients that you want to get the letter> rather than <my entire client list of 800+>.
 - For example, if they all share the same F4/status, you can look for field c1_g4 (current status).
 - Other useful limitations are: c1_g17 (preparer, on the signature line), c1_56(staff preparer), c1_g13 (person who initialed current status), and c1_25 (custom filter).

Also, if your source document for the merge already has things like watermarks & letterhead formatting [i.e. "things that make the file large"], you may benefit by keeping just the plain-text version to get merged in, and then adding the "pretty" bits after the pages exist.

Robert

[whartman]

Unfortutately, these letters are created on the fly since some of the info is not known until the tax return gets mailed.

I dont see a way in the ODBC configuration for the Lacerte Driver to query specific columns.

Can you point me?

Thanks.

[DatabaseRobert]

That's why I was asking how you were going about it.  For example, if you set up your data link in Excel, then you can query/limit your number of people there...  and generate the letters only for those few that match the criteria.

This discussion might materially benefit from you describing how the clients are selected, rather than in generalities..
  If they have something in common ("always have FormX" or "AGI > some amount with non-taxable Pension amounts") then it can be set up as a query.
  If the particular clients are chosen manually...  yeah, there isn't a great deal that can be automated about that.