#error on textbox

[Cris]

I have two continuous sub-forms with calculated textboxs on the form footer. The formula it is just the sum and product of the values of every record. I haven't had problems until a user complaines it is getting on the textboxes this "#error" message on both sub forms. This happens randomly and it fixes if the user moves to another record on the main form and then he come back to his record.

I've not been able to reproduce the error (but the user send me an screen shot) and I have not idea why I am having this problem suddenly since the formula appears to work correctly.

The Access version is 2003 and the back end is on a shared drive while the front end is on user's computer.


Thanks for your ideas.

 

[vbaInet]

It would be useful to see the exact calculations?

Also, are the fields you're adding up Number or Currency datatypes?

 

[Cris]

These are the calculations

First subform

three textboxs
=Sum([HreTravaille])

=Sum([HreAttente])

=Sum([HreReparation])


HreTravaille is Number (single)
HreAttente is Number (single)
HreReparation is Number (single)

Second subform

=Sum(([Nombre]*[NbreHreRegulier])+([Nombre]*[NbreHreSup]))
Nombre is Number (field size Byte)
NbreHreRegulier, NbreHreSup are Number (Single)

Thanks

 

[vbaInet]

Does the first one give problems too?

For the second, what you can do is:

1. Create a column in the query to perform this calculation - ([Nombre]*[NbreHreRegulier])+([Nombre]*[NbreHreSup])

2. Then perform the Sum on that field - Sum([AliasField])

 

[Cris]

Yes, I have the same probleme in both sub forms.

For you suggestion, I just wonder if adding this calculation to the query would have an impact on the execution time of the query.

Thanks

 

[vbaInet]

I can't think of why the problem is intermittent but it may well be network problems. Or even corruption creeping in. Have you experienced any other problems? Also, have you tried running the db locally to see if the problem persists?

I think you would find that it would run slightly faster since the core of the calculation is done in the query for all the selected records.

 

[Cris]

Concerning the network problems, A user lost communication whit the database due to network problems but it didn't happend again. Besides, I have been experienced slow performace with his network which will make me think that this could have caused the problem. However, i have other users that had used the application on a key usb(front end and backend), and they have experiment the same problems. So, i cannot be sure of what causes the problem since i not been able to reproduce it.

I could try to change the calculations to the query but I wonder why the first form has the same problem since it doesn't have calculations

thanks for your replies

 

[vbaInet]

Using a flash drive for Access is generally not advisable. So still you would need to test it locally first, unsplit and NOT on a key to see if you still have problems.

 

[missinglinq]

Using a flash drive for Access is generally not advisable.

In point of fact, using a flash drive for Access is a terrible idea! I've been in forced retirement for five years now, and generally spend 8-10 hours a day cruising and contributing to 6 or 7 Access forums, and the number of reports of corruption and other problems secondary to USB flash drive usage are legion! You really should never use one in conjunction with Access unless you are absolutely positive that you have the app backed up elsewhere and are willing to deal with the loss of data entered after this backup is made.

The only factor I've seen put forward as a possible cause is that a lot of flash drives apparently prematurely indicate that the data transfer is complete when, in fact, it isn't. The interrupted transfer then corrupts the file, just as the dropping of a network can do if it occurs in mid transfer.

Linq ;0)>