Dennis,

Buddy's recommendation on the SCRATCH setting is #1.

When RBG7 loads a form it is going to pull down all of the LOB data for the form, and that includes the eeps embedded in the form. From a network traffic perspective, this is probably a better approach, assuming scratch files are written locally, than using external eeps since an external eep will traverse the network every time it is invoked.

The message about being unable to complete a write of the rb1 file is a very serious issue that will certainly lead to a corrupt database very quickly. This could be the result of a number of issues - bad NIC, bad cable, bad hub/port, cache settings on the server, etc. To diagnose: does it happen to only one or a couple workstations, or everyone? If everyone, look at network infrastructure and the server; if only one or a couple, look for commonalities such as network distribution lines, hubs, etc. If only one, look at the workstation, its NIC, cable and the hub/switch port.


Upgrading a customer from 6.5 to 7.1 and seem to have uncovered a slow network at one site. Hubs, switches, routers, etc., it all comes down to band width and overall speed. I know switches are fastest but (in hindsight) it would have been better to let them know they needed to improve their network before I loaded 7.1

With an RB4 file of about 4mb (~ 100 forms), I thought it should be a fairly smooth transition for most of our customers. Not sure how much of file 2 and 4 need to be pushed out to each user at runtime. With virtually all my code in forms this apparently is too much overhead for a few users. Nasty Windows message about not being able to complete a write of "mydbname.rb1". Assuming RBase trying (unsuccessfully) to keep the data base in sync.

Any workarounds appreciated.

Dennis
*****
Dennis Fleming
IISCO
http://www.TheBestCMMS.com
Phone: 570 775-7593
Mobile: 570 351-5290

Emmitt Dove
Manager, DairyPak Business Systems
Blue Ridge Paper Products, Inc.
40 Lindeman Drive
Trumbull, CT  06611
(203) 673-2231
[EMAIL PROTECTED]
[EMAIL PROTECTED]

Reply via email to