Tim, I'm not sure I have an answer for you on this one, but have seen
something similar. Client used A2000 (under Win2000), and their server was
WinNT. Intermittently, the calculated controls would show #Error, and the
drop-down lists would not load all values (e.g. only the first 30 or 50
where there should have been 200 items). There were 3 or 4 subforms, each
bringing a subtotal back to the main form which provided a grand total.
Upgrading all their workstations to JET 4 SP8 and Office 2000 SP3 did
improve the situation (esp with the drop-down lists), but we never
completely solved the #Error. I was unable to repro this on my (less busy)
network, so we concluded it was probably a timing issue: persumably Access
was timing out before it could load all the subform records, calculate the
subform totals, and bring the values back to the main form.
If anyone else has suggestions or experiences, we'd love to hear about them.
BTW, one thing worth checking out would be the service pack of the Win 2000
Server machine. It's crucial that Opportunistic Locking is off on the
server. From memory SP3 for Win 2000 Server did that.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"tconway" <tc*********@earthlink.net> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...
I have an Access program that displays Customer data into a form and
OrderID data into a subform. The totals in the Subform are based on
calculated fields, i.e. the Total Amount field Calculates the
following: =[Quantity]*[UnitPrice]
The Subform Order fields are pulled from a Query along with each
calculated Total. They are displyed in a DataSheet View.
This works fine on my developement environment which includes a server
set up just as our client has. But at the client's site, the
calculated field is intermittent, will appear if you click on it,
disappear if you scroll the field out of view, or two or three
calculations will show, others won't.
Although I am unable to repeat this behaviour in the environment I work
on, two systems I have set this up on show the same problem.
Any idea of how to fix this?
All systems are on the following
XP SP1 workstation
Access 2000 SP3
Win 2000 Server
Thanks
Tim Conway