At 04:12 PM 2/19/2013, Javier Valencia wrote:
As part of an ongoing issue with screen flickering, we have determined that
the issue happens only on the Windows 7 workstations. While trying to set
the application to the compatibility mode, a message is displayed indicating
that this setting cannot be changed on a network drive.
I am thinking about installing copies of the executable on the local drives
to see if it helps, and where we can try running it in the compatibility
mode. I was thinking about creating an external form front end that checks
the current version against the one in the server and if a newer version is
found, it would copy it to the local drive; has anyone done something like
this? If yes, are you using the mapped drive path or the UNC path to the
database files? Is there an advantage in using one over the other? TIA.
Javier,
FWIW ... you may want to take a close look into the Win 7 Professional (32/64)
installation, hardware and video settings. Make sure that all important
updates (MS Win 7 and R:BASE) are applied accordingly.
All my BIG corporate and government clients use R:BASE eXtreme 9.5 (64),
compiled and non-compiled applications in a local, WAN, and TS environment
without a problem. Not to mention the shared web applications using Oterro
9.5 (64) running on MS Windows 2008/2010 server with Apache/PHP.
Some complex applications accessing multiple R:BASE eXtreme 9.5 (64)
databases take full advantage of External Form Files.
All compiled applications are shared and running on the network and not on
individual workstations.
Hope that provides you with some blue's clues ...
Very Best R:egards,
Razzak
www.rbase.com
www.facebook.com/rbase
