I had a similar problem when I upgraded from 7.6 to 9.0(32).  The 7.6 app had 
worked fine at 3 different locations, on 3 different networks(4-6 computers 
each).  When I started the app on the host computer, everything was fine, but 
when I tried to start on any network computer it locked up.  Thru alot of trial 
and error I finally tracked it down to a variable image that was used in my 
main 
menu(it was about 1 meg jpeg).  When I took it out of the startup eep 
everything 
was fine.  I ended up just putting the image as an image in the main menu.  
Nobody gave me a reason for this.  My app was a direct upgrade of my startup 
file from 7.6 compiler to 9.0 compiler, with absolutely no changes.  You might 
check to see if you have a similar situation.
Tom Hart





________________________________
From: Luc Delcoigne <[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Tue, October 5, 2010 2:52:11 PM
Subject: [RBASE-L] - re: network trouble


Hi, 
 
I have developed an application in R:base 9.0 (64) under  Win 7.
 
This application runs fine and fast when run on one  PC.
 
the latest version of R:base is installed on my  PC's.
 
When I put two recent PC's in a network via a 100  Mbit/sec switch, with the 
database in a shared directory on PC A, it still runs  well on PC A, but when I 
log in from PC B, it goes SLOW on this PC and  eventually locks up, so that I 
have to restart R:base on PC B.
(PC A : 6 GB RAM, 1 Tb HDD...PC B : 4GB RAM and 500 MB  HDD)
 
I don't dare to image what a disaster this could in a  small network with 5-6 
workstations.
 
It must be that I am overlooking something in the  network setup.
 
Could anyone give me 'to do'list on what to do exactly  and in what order so to 
get a workable network application.
 
This network thing is the last step I have to make in my  conversion from 
Access 
to R:base.
(sometimes I begin to regret I didn't stick with  Access...as far as this 
network thing is concerned)....
 
Any help would be greatly appreciated....
 
Luc Delcoigne

Reply via email to