Dan,

A couple of things you may want to check into. When I had similar problems some 
of these were causes.

1)      Do you put a TIMEOUT into your DAT file for the compiled apps? Prior to 
having this code in the DAT file, I ran into "Phantom" connections. So my 
connections kept increasing.

2)      If some of your users are running remotely, the double click will 
sometimes give you the "cannot connect to database" error. They may be triple 
clicking. I have had that happen.

3)      When you say you have corruption, do you see this when you do the 
unload/load? Or what shows you have corruption? RSCOPE?

James Belisle

Making Information Systems People Friendly Since 1990
[cid:image001.jpg@01CD8CE2.FB048F50]

From: rbase-l@googlegroups.com [mailto:rbase-l@googlegroups.com] On Behalf Of 
Dan Goldberg
Sent: Thursday, January 26, 2017 9:54 AM
To: rbase-l@googlegroups.com
Subject: [RBASE-L] - At my wits end

For a while now I have been battling with regular database corruption that 
happens at least every other week. Also we get a lot of "cannot connect to 
database" when opening rbase or compiled apps.

I have checked every computer to see if there are any issues that connect to it 
as well as power saving feature, moved the database to a new server without any 
luck. I get the "cannot connect to database" on the server that is running a 
compile app locally from time to time as well.

I have done a complete database unload/load several times to find any 
underlining errors but no avail.

It is like a needle in a haystack and it is frustrating.

I was thinking something to do with our Anti-virus(Avast for Business) but the 
server is not running one.

Anybody have any pointers on how to figure it out the source of corruption?


Dan Goldberg

________________________________

-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbase-l+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to