Dim on a Network

[DS]

Any dangers or suggestions on using Dim on a Network where several
users will be access the same form?
Thanks
DS

 

[Rick Brandt]

Any dangers or suggestions on using Dim on a Network where several
users will be access the same form?
Thanks
DS

Variables are in memory on each PC. You shouldn't be having multiple people
opening the same front end file for LOTS of reasons, but variable scope is
not one of them.

 

[DS]

Variables are in memory on each PC. You shouldn't be having multiple people
opening the same front end file for LOTS of reasons, but variable scope is
not one of them.

Its an order input screen where multiple users will inputing records at
the same time. Each user will have their own PC. The database will be
split as well. Is this a can of worms?
Thanks
DS

 

[Rick Brandt]

Its an order input screen where multiple users will inputing records
at the same time. Each user will have their own PC. The database
will be split as well. Is this a can of worms?
Thanks
DS

If the database is split (good idea) then each PC should have its own
(local) copy of the front end file. Sharing a common front end often leads
to corruption problems.

 

[Keith W]

Its an order input screen where multiple users will inputing records at
the same time. Each user will have their own PC. The database will be
split as well. Is this a can of worms?

Not at all, provided that you give each user their own FE. There are simple
ways to ensure that this happens automatically, I use simple batch files to
copy the FE from the server to the PC and then open it. This ensures that
the users always get a compacted and latest version of the file.

HTH - Keith.
www.keithwilby.com

 

[DS]

Not at all, provided that you give each user their own FE. There are simple
ways to ensure that this happens automatically, I use simple batch files to
copy the FE from the server to the PC and then open it. This ensures that
the users always get a compacted and latest version of the file.

HTH - Keith.
www.keithwilby.com

Great Thanks, So do I have to run this batch file everytime, or can the
front end just reside on that PC.
Thanks
DS

 

[DS]

If the database is split (good idea) then each PC should have its own
(local) copy of the front end file. Sharing a common front end often leads
to corruption problems.

Thanks Rick, I thought I was heading for a disaster!
DS

 

[Douglas J Steele]

Great Thanks, So do I have to run this batch file everytime, or can the
front end just reside on that PC.

The FE should reside on the PC. What Keith's suggesting is a way to ensure
that each user always has the most recent version of the FE. By putting a
copy of the FE on the server, and using a batch file to copy from the server
to the PC, you can place new versions of FE out there without having to
visit each PC.

 

[Rob Oldfield]

Not at all, provided that you give each user their own FE. There are
simple

ways to ensure that this happens automatically, I use simple batch files to
copy the FE from the server to the PC and then open it. This ensures that
the users always get a compacted and latest version of the file.

HTH - Keith.
www.keithwilby.com

Just for reference Keith, there's a little util called runh here
http://helpdesk.kixtart.org/KixUtilsMisc.asp that allows you to run batch
files hidden. I do much the same as you and it works well for me.