Reflex_ht
Registered User.
- Local time
- Today, 00:02
- Joined
- Sep 11, 2012
- Messages
- 64
Hallo,
Eveywhere on the Net I read that the bast way to run a MS Access application is to split it and to save the BE on a network and the FE on a local PC.
OK.
I have a application that is splitet from the begining but at the first months it was runing FE and BE from a network and i had no problems with that.
Now I made a automatic update funktion for the FE and of course one FE can´t be used by more than one user. At first the FE was saved on the local PC of the users reading the tables over linked tables from the BE stored in the network. It hapens that one user that uses hes privat laptop at work witch has the same settings like the company PC-s was runing the application very (I mean very very) slow I like trying more solutions for everihting I do so I just run the FE on that laptop from the network and it had the same speed like the others ???? Why that when everyone says that it should go the other way faster??? Its not a problem for me but i got little confused
A notices also a other thing: when all users open the same FE from the network thay can work with the data very easy. Now that i split the FE in more and thay use they'r own FE´s it hapens sometimes that records arent shown to the other users, simultaniouls working is harder, deleting records also make some curious things. I had much les problems and much more speed runing the application the OLD (WRONG) WAY
OK. The lower speed could also be because of adding two tables to one but the example with the privat laptop showed me that there are some things that can slow or speed up the application withoud changig enithing but the position of the accdr file withc is used as FE.
P.S.
Because the app runs on a network faster I made on the network a folder for each PC (there are just 5 and there wont be more) and in every one is a bat file that runs the update. The folder names are the PC names of the users. In the FE is a funktion that shedulles the bat file for a update. The path to the bat. file has a variable (the last folder name) and because it has the name of the user PC I just determin his value with the Environ("COMPUTERNAME") funktion.
Now the question
What can i do to make the app faster. It works just with one table (big) (about 20 000 records) where the users insert and edit records. The table dlookup values forom other tables and saves them in the main table. Linking tables is no solution because other tables are changig very often and that could delete data in the main one. Working with linked tables has for me no benefits (for now). We'r also waiting for a SQL server to be installed. That should make it also a bit faster
Eveywhere on the Net I read that the bast way to run a MS Access application is to split it and to save the BE on a network and the FE on a local PC.
OK.
I have a application that is splitet from the begining but at the first months it was runing FE and BE from a network and i had no problems with that.
Now I made a automatic update funktion for the FE and of course one FE can´t be used by more than one user. At first the FE was saved on the local PC of the users reading the tables over linked tables from the BE stored in the network. It hapens that one user that uses hes privat laptop at work witch has the same settings like the company PC-s was runing the application very (I mean very very) slow I like trying more solutions for everihting I do so I just run the FE on that laptop from the network and it had the same speed like the others ???? Why that when everyone says that it should go the other way faster??? Its not a problem for me but i got little confused
A notices also a other thing: when all users open the same FE from the network thay can work with the data very easy. Now that i split the FE in more and thay use they'r own FE´s it hapens sometimes that records arent shown to the other users, simultaniouls working is harder, deleting records also make some curious things. I had much les problems and much more speed runing the application the OLD (WRONG) WAY
OK. The lower speed could also be because of adding two tables to one but the example with the privat laptop showed me that there are some things that can slow or speed up the application withoud changig enithing but the position of the accdr file withc is used as FE.
P.S.
Because the app runs on a network faster I made on the network a folder for each PC (there are just 5 and there wont be more) and in every one is a bat file that runs the update. The folder names are the PC names of the users. In the FE is a funktion that shedulles the bat file for a update. The path to the bat. file has a variable (the last folder name) and because it has the name of the user PC I just determin his value with the Environ("COMPUTERNAME") funktion.
Now the question
What can i do to make the app faster. It works just with one table (big) (about 20 000 records) where the users insert and edit records. The table dlookup values forom other tables and saves them in the main table. Linking tables is no solution because other tables are changig very often and that could delete data in the main one. Working with linked tables has for me no benefits (for now). We'r also waiting for a SQL server to be installed. That should make it also a bit faster