By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,665 Members | 2,802 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,665 IT Pros & Developers. It's quick & easy.

Calculated value invisible until been clicked

P: 9
We are running Access 2010 runtime on Server 2008 R2 with both FE and BE on it. Each user has own FE copy on Server which is opened from own PC through remote desktop.

After fresh Server restart all goes well for 1-2 weeks. But then some strange behaviour starts:
- values of all calculated fields - whatever, on forms or on reports - disapears. When I click on a field it shows up again. And refresh does not help;
- all condition formats does not show up until I hover the mose on it.

When we restart the Server all comes to normal again. Its very annoying because users thinking data are gone!

I have searched a lot on net but seems it is rare problem and maybe related to some kind of overcaching or something related to time used.

Would be great to hear from you of any help on it.
Jan 9 '14 #1

✓ answered by zmbd

Ok... so each user has a copy of the frontend... this is good.
The copy is on the server, this is a bottle neck.
- server feeds to local pc
- local pc makes request
- local request feeds to server
- server handles request
- server then feeds update to frontend display
- server then feeds data up to the frontend display

--
- each user has own copy on local pc
- the front-end sends request to server
- server processes and sends data back up to front-end
- local pc processes the data

You can still use the idea of the script,
Have the user click on the button
Have the script check for local pc version against server version of frontend (if change then download newer version, if no change then start the application).
This is what our IT does. We have a MySQL based system. The frontend is all in a flavor of C, there is a launcher script that checks the server for new versions and installs the newer version, then launches the frontend.

Share this Question
Share on Google+
8 Replies


zmbd
Expert Mod 5K+
P: 5,287
See if the following will help...
ACC2100
You need to open the front-end master.
Backstage (File on the ribbon)
Options
Current Database
(scroll down)
Caching Web Service and SharePoint tables
Select: Use the cache format that is compatible with Microsoft Access 2010 and later
Select: Clear Cache on Close
Save
Push this new frontend down to the users.
Jan 9 '14 #2

P: 9
Thanks for reply a lot.
I'll do it today for all front ends. We do not use neither Web nor SharePoint but who knows, maybe it helps. Be back with results after few weeks.
Still if anyone have other suggestions would be nice to hear.
Jan 10 '14 #3

P: 9
As promissed I am back with test results. Unfortunately it did not help but now it is certain that our problem is directly related with thin client of remote desktop. So, nothing to do with Access. Still question is open and if somebody has resolved it would by great help for us.
Apr 7 '14 #4

zmbd
Expert Mod 5K+
P: 5,287
one more suggestion then, push the frontends down to the local pcs... don't run them from the server.
Apr 7 '14 #5

P: 9
It helps for sure to resolve this problem but then I loose control on FrontEnds. We have BackEnd based on Access. To make maintance I need to close all FrontEnds (30 users). On Server it is not an issue but on individual PC's - how can I manage it?

P.S.: I know that such many users must run on more serious DB, such as SQL SERVER. We plan to move there but it is different story...
Apr 8 '14 #6

Expert 100+
P: 1,221
You could add a data item to a parameter table, something like
DBClosed_yn and then write a function that returns the value. Add calls at appropriate places throughout your software,
Expand|Select|Wrap|Line Numbers
  1. if DBClosed() then
  2. msgbox "The database is closed for maintenance"
  3. docmd.quit
  4. endif
  5.  
Then when you need to do some maintenance you just set the flag and wait for everybody to encounter it and exit. The waiting might be the hard part.

I wrote a menuing system that allows me to see who is logged in and what version they're running. I can retire a version, which forces people on that version to update before selecting anything on the menu. I think I'll add this feature to it.

Jim
Apr 8 '14 #7

P: 9
Hi Jim, thanks for the suggestion.

We have 10 users in office and 20 users in production (their do scan all the products at every prod. proccess point). Office works 8 hrs / 5 days but production do 24 hrs / 7 days and here is the problem. In fact we nether have situation when all FE are logged off.

I have FE versioning done through vbscript. Every time user clicks the script file the FE (master) copy goes to separate folder, gets individual file name and starts Access runtime.

I never thought this approach is bad. At least I cannot find the reason "why?" because in my structure every user has own copy.
Apr 9 '14 #8

zmbd
Expert Mod 5K+
P: 5,287
Ok... so each user has a copy of the frontend... this is good.
The copy is on the server, this is a bottle neck.
- server feeds to local pc
- local pc makes request
- local request feeds to server
- server handles request
- server then feeds update to frontend display
- server then feeds data up to the frontend display

--
- each user has own copy on local pc
- the front-end sends request to server
- server processes and sends data back up to front-end
- local pc processes the data

You can still use the idea of the script,
Have the user click on the button
Have the script check for local pc version against server version of frontend (if change then download newer version, if no change then start the application).
This is what our IT does. We have a MySQL based system. The frontend is all in a flavor of C, there is a launcher script that checks the server for new versions and installs the newer version, then launches the frontend.
Apr 9 '14 #9

Post your reply

Sign in to post your reply or Sign up for a free account.