|Subject:||Re: Performance problem opening database on SQL-server
|Date:||Mon, 23 Mar 2020 08:35:52 -0400
|From:||"Steven Green" <firstname.lastname@example.org>
using ordinary paradox tables, we've seen several instances over the past
few months where two different access sets have different results.. the
ordinary network logins are fine, but on the terminal server logins, one
table or one file will refuse to cooperate.. disturbingly similar to your
in each case, even completely deleting and replacing the table failed to
change anything.. after a few days, the problem went away, each time.. it's
like a file name got stuck somewhere
Myrtle Beach, South Carolina, USA
Collectibles and Memorabilia
Vintage Lego Sets and Parts
- and Paradox support, too
"Anders Jonsson" wrote in message
Den 2020-03-22 kl. 23:48, skrev Leslie:
> Have you checked things such as a Hardware/Software VPN?
Not in detail, but
Ping values to the server is normal
Regular surf to the Internet is normal
I have no problem to rdp to the pc.
In normal case, I would say there is a network error of som sort, like a
faulty NIC but that doesn't expalin why just one db is effected.
I spent this morning writing different test routines and I always get
the same result:
- My testenvironment with a mix of Windows 7 and Windows 10 has no
problem. Not to my test SQL server, not to the production server.
- In one shop, everything is OK
- I the other shop, I have one problem, and only one - that is to open a
database variable to one of the databases. Once opened, select and
insert works OK. The second database - no problem.
I can repeat this over and over again.
I have seen many strange things in my life, but this i really something
Thanks all for your input, I guess I will have to setup another PC and
try with that.