Re: Problems with SQLEXEC
- From: somnat@xxxxxxxxxxx
- Date: Wed, 21 May 2008 17:55:29 -0700 (PDT)
On 22 May, 01:43, "Dan Freeman" <s...@xxxxxxxxxxxxx> wrote:
You cannot fix a network problem from inside VFP.
The best you can do is catch the error and die gracefully. See Try/Catch in
the help system.
That said .... you don't mention which version of VFP. Connections behave
differently in the latest versions so troubleshooting advice may vary as
well.
Dan
Somnath Gupta wrote:
While executing SQLEXEC to pass a SQL statement (ranging from simple
to complex) on a previously connected (using SQLCONNECT) valid ODBC
connection to a SQL server on a newly installed network, the error
handler sometimes (at random) is reporting SQL Server communication
failure resulting the whole execution to crash. Any ideas how to
resolve this problem ? I have suspected that it may be transient
network conditions but nothing more.
Warm Regards
Somnath- Hide quoted text -
- Show quoted text -
The Error handler is doing what Try/Catch is supposed to do, i.e.
dying out gracefully so I dont see any necessity in changing the code
there, but how can I establish to the client it is a network and not a
VFP error ? Users always have the idea that
the software is at fault. The Version of VFP is VFP 9 SP2.
Warm Regards
Somnath
.
- Follow-Ups:
- Re: Problems with SQLEXEC
- From: Dan Freeman
- Re: Problems with SQLEXEC
- References:
- Problems with SQLEXEC
- From: Somnath Gupta
- Re: Problems with SQLEXEC
- From: Dan Freeman
- Problems with SQLEXEC
- Prev by Date: Re: How to convert a TIF file to PDF under VFP?
- Next by Date: Open table owninf DataBase
- Previous by thread: Re: Problems with SQLEXEC
- Next by thread: Re: Problems with SQLEXEC
- Index(es):
Relevant Pages
|
