Muli-user access very slow

[jamie07051975]

I have written a system in VFP6 to hold football fixtures.&nbsp;&nbsp;The system is split into a main executable (.exe) which runs the menu which calls several applications (.app).<br><br>My problem is that when two workstations access the system it slows down and takes around 3 minutes to display all the fixtures on the system.<br><br>But, if I run the system on one machine only the system takes around 3-4 seconds to display the fixtures.&nbsp;&nbsp;If I run the system on one machine more than once at the same time it still only takes around 3-4 seconds.<br><br>I can't believe it is the network as it's handling the same amount of traffic.<br><br>I have tried several types of machines as the server (some more powerful than others) but with no apparent differences and have tried several different machines as the workstations, again with no difference.<br><br>Is the system slowing down as a result of using .apps or is there conflict with who can use the files on the server at one time and therefore slowing each other down (although it doesn't slow down if one machine runs the system more than once at the same time????)<br><br><br>This is now hurting my head.&nbsp;&nbsp;Can someone please help me?<br><br>Thanks,<br>&nbsp;&nbsp;&nbsp;&nbsp;Jamie Richards

 

[BlindPete]

Is only your data shared?<br>Or is the EXE also shared?<br><br>Having the EXE local will increase performance significantly if it is not already. <p> Pete<br><a href=mailto:blindpete@mail.com>blindpete@mail.com</a><br><a href= > </a><br>What your mother told you is true! You will go blind! (from moonshine anyway)

 

[sdcabq]

Try using buffered forms and tables. It will work much better. It does not matter whether the executable is on the server or local machine. The spped of the application is determined by how the tables are used. I have over 300 users accessing a very complex database with 185 tables and about 30,000,000 records and retrieval time is usually less than 3 to 4 seconds.

Also, try using foxpro retrieval language (seek, etc) rather than SQL. Also do not use views if you want speed. Views retrieve the data into temporary tables and take a long time to populate.

For grid objects and combo boxes and lists, leave the rowsources empty until form initialization, then insert the sql statement into the object's rowsource field. This will load much faster.

 

[foxdev]

It does not matter whether the executable is on the server or local machine.

I generally agreed with most of your other comments, but disagree here. True, on a fast, light-use network it may make little difference, but on a slower or heavily-used network or with an overburdened file server, placing the EXE and support files on the local machine may make a significant difference, depending on the size of the app.

Robert Bradley

http://www.foxdev.com/

 

[foxdev]

...but let me clarify: it may make a significant difference in the overall performance of the application as perceived by the user, not in the query performance.

Robert Bradley

http://www.foxdev.com/