Re: Problems with SQLEXEC

Tech-Archive recommends: Speed Up your PC by fixing your registry

On May 23, 2:07 am, "Dan Freeman" <s...@xxxxxxxxxxxxx> wrote:
som...@xxxxxxxxxxx wrote:
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

When we have a client that experiences this sort of thing and we suspect the
network, we tell them to set the application up on a stand-alone machine
that has no network connection at all.

When they come back to us, they always have a mystified tone in their voice.
"It works just fine." Even then, we have to hammer home the point that all
we removed was the network. <s>

Dan- Hide quoted text -

- Show quoted text -
Dan/Olaf

Thanks to both for your time.

The original code traps -1 correctly and logs the error correctly.
However I am not interested in error trapping to be precise, as the
same network handles a lot of different application with only the VFP
application erroring out. You are right Dan, no network no worries but
that is not how the real scenario is supposed to be. Even a simple
command like 'SET LOCK_TIMEOUT -1' is sometimes crashing through
SQLEXEC and the client has got good SQL programmers on board and they
are using other SQL apps all the time with the same client/server link
without any single problem. Of course this has started happening after
we upgraded them to VFP9.0 SP 2, so the client tells it is neither
network or SQL Server and they have a point.

Warm Regards
Somnath




.

Relevant Pages

  • Re: server disconnection - very often
    ... Often get the redirected folders working offline prompt on some client ... VMware virtual network interface cause network issue. ... On the Connection Type page, click Broadband, and then click Next. ... |> re-initialize the offline files cache and database on client computers: ...
    (microsoft.public.windows.server.sbs)
  • Re: server disconnection - very often
    ... Reason of permanent popups is VMware server aplication on clients. ... Run CEICW to configure the network of SBS: ... Two network adapters - manual router connection to broadband ... Uninstall VMware on client. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connection from remote computer to network SQL Server
    ... There is no firewall on the W2K machine acting as the SQL server. ... I tried making the SQL machine a "trusted" on the router. ... connection works. ... To find the IP address of your computer inside the network, ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Lan Wifi Network
    ... >knowledge of computer network... ... a wireless user has gone away. ... client software to do the job. ... connection which can be timed. ...
    (alt.internet.wireless)
  • Re: Remote Client Configuration
    ... the client computer to the SBS domain via connect computer wizard remotely. ... local network or via dial up VPN connection, you will use an local copy on ... connection is established, Group Policy is not applied during logon. ...
    (microsoft.public.windows.server.sbs)