Jim,
Follow these steps to narrow down the exact problem:
01. Make sure that there is no one connected to the database in question
02. Go to the first workstation and start R:BASE 6.5++
At the R> prompt:
SHOW STATICDB
Switch the default drive and directory where the database is
CONNECT dbname
If you are able to CONNect successfully then leave the database
connected and go to the second work station and follow the same
step as above. If you are able to successfully CONNect from all workstations,
then, you know that there is no problem as far as manually
connecting the database.At this time, you can DISConnect from all workstations is you wish.
03. Now try the normal process using your icons/shortcuts, etc., one
at a time and see which workstation is having the problem CONNecting
the same database. Then, you need to compare the default R:BASE
configuration (RBASE.CFG) and set setup (RBASE.INI) files for that
particular workstation.Other Suggestions:
01. Make sure to RELOAD the database to rebuild all INDEXes, etc.
02. Make sure that all users have the privileges to read/write/delete
to create and delete TEMPorary files, used during the R:BASE session.Good luck!
Very Best R:egards,
Razzak.
At 07:50 PM 1/5/2004 -0600, Jim Van Dillen wrote:
We are using version 6.5++, so there is no problem about us using the latest and greatest.
The file were originally copied from one computer to another. The "read only" attributes have been checked a number of times in attempting to solve this problem.
I would appreciate some HELP as this is seriously damaging our day to day business.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of A. Razzak Memon Sent: Monday, January 05, 2004 7:02 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Network setup of RBase - Razzak's Reply
Jim,
First, what version and build of R:BASE are you using?
In reference to "Read Only" attributes for files copied on the server, my guess is that you have copied those files from the CD. If that is the case, then, all files copied from the CD will be Read-Only. Use the Windows File/Folder Properties option to un-check the "Read-only" option.
If you're using a legacy version of R:BASE, you may need to configure the SERVER5.SYS or SERVER6.RBG file accordingly. There is no such hassle in the latest version of R:BASE 6.5++ or R:BASE 7.0.
Hope that helps!
If you need further assistance, feel free to ask.
Very Best R:egards,
Razzak.
At 06:38 PM 1/5/2004 -0600, Jim Van Dillen wrote:
>I have been using RBase since 1986, switching to the Windows version in >2000. We have a small office with 6 users networked together. > >We have been running Windows NetBIOS until recently when we switched to >Windows 2003 Small Business edition as we wanted to close up our system to >others in the our bulding who are on the same physical network but in >different workgroups. > >When we first set up we made all users both domain users and domain >administrators just get things going with the intention of customizing the >security for the various users further down the line. Initially we >couldn't get access but it turned out the files were marked "read only"
>when we copied them to the new server. > >Since then the network has been working but we have been having random >disconnects from the RBase data file and many times it takes several >attempts to get the database to connect. When we try to connect manually >we get the message that we can't connect since that the database is >already open with STATICDB ON and we are trying to connect with STATICDB >OFF. In the past this usually meant that the data file was "ready only" >for some reason. I suspect the there is something set wrong in the >security or permissions settings but the fact that we are able to connect >some of the time baffles me. > >I would add that we run RBase from the server is this seems to work the >fastest and makes modification easier although I have tried running Rbase >on my local workstation, accessing the data file remotely. I still get
>the same random disconnects and/or refusals to connect. > >The access to the server and rest of the network is fine so I don't >suspect a hardward problem. The problem seems to only exist with RBase
>access. The problem is seemingly random among users and workstations and >is starting to cost us considerably in both time and money. > >Has anybody any thoughts as the cause and solution to this problem? >Any >help would be greatly appreciated.
