Aiko - In my experience, the error message "Waiting for Required Resources" means that there is a problem with the user's connection to the network. It may be a NIC card, the cabling, a hub or router - but the message just means that for some reason R:BASE cannot send or is not getting back a valid response to the database on the server. It is not an R:BASE problem but a network problem.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Sami Aaron Software Management Specialists 913-915-1971 [EMAIL PROTECTED] -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Aiko Ichimura Sent: Tuesday, March 13, 2007 11:05 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: V 6.5 I just send in an order for the upgrade. Thank you for the push. I look forward to seeing the greatly improved version. In the mean time, I am trying to figure out a problem my clients are having in 6.5+. It seems that when it's in the multi-user mode, number of people can access a form with no problem;however, if a user run a program and try to update the table, Rbase issues warning saying"Unavailable resources...". I have inserted "Wait" statement to increase the length of waiting before it gives up. But many people are using forms that engage the same table and there is not much chance for the program to be successful unless this user asks everyone to get out of Rbase. Program runs beautifully once everyone is out. But this is really a problem for my clients since the terminals are located in a huge building and could not possibly run around ask people to get out. I advised them for the moment to run the program early in the morning or late afternoon when people are not on the Rbase system. I would like to figure out something to allow the clients to run the program without asking everyone to get out. Increasing wait time is not ideal solution though. I can't understand why forms allow access to the same table to multi-user updates and not from a program. While I was searching I found a command " SET ROWLOCKS ON/OFF " in the help document and it explains: Default: ON Mode: Multi-user R:BASE uses row-level locking in a multi-user environment. This command causes R:BASE to lock only the required row for the current command instead of locking the entire table. For example, if multiple users are modifying the same table using the UPDATE command, R:BASE locks only the rows affected by each UPDATE. When ROWLOCKS is set off, R:BASE sets table locks during each UPDATE, regardless of how many rows are affected. Is this the answer to my problem? Should I put this in m,my program before the update statement? If default is "ON" why it's not working right now? Has anyone been successful in tricking the system using this command ? Thank you for your advice always. Aiko Ichimura [EMAIL PROTECTED]
