How to wake up an odbc connection

[Walter D Vaughan Jr]

> -----Original Message-----
> To: fplist
> Subject: How to wake up an odbc connection
> When I manually go to run this batch file about 40% of the time I get the
error
> that a connection could not be established.  If I break out of it and
rerun the
> batch all works well.  This only happens on the first call for a
connection.  It
> looks like the ODBC link needs to be awakened.
> 
> Anyone have any thoughts?

[Walter D Vaughan Jr] 
Maybe you don't need the overhead of ODBC?
Did I read it correctly that you only are updating from SQL Server to
filePro?

What about using sqlserver's "sqlcmd" command to export data as .txt or
.csv,
Then have a filePro table(s) read in that data as a wedge layer that can be
used to stage the data prior to importing into your permanent filePro home
data. IIRC sqlcmd runs pretty much lightspeed, so it's just a matter of
running the filePro import command which IIRC run pretty fast as well.

I wonder if indexes are killing you on the import side as well. Maybe you
could delete them, import your data, then recreate them.

Two hours is what we put up with 25 years ago, not today.