Getting #ERROR# in subform

[Dennis Snelgrove]

I've got a front-end that I'm running on 5 different PCs in our office. One
of the forms has a continuous subform with a textbox that shows the
formatted time, and this is a calculated field from the form's recordsource
query. On 4 of the 5 PCs, the subform works perfectly; on the 5th I get
nothing but "#ERROR#" in the time textbox. All the rest of the form works
perfectly, though. The first record in the subform shows the proper time,
the rest show "#ERROR#", and if we scroll the subform at all, that first
record also goes to "#ERROR#".

I've checked that the front-end is the same as the other 4 PCs, and it is.
I've checked the Regional Settings, and they're no different. I've run the
source query itself and the output is proper for the entire recordset; it's
just when the recordset is fed to the subform that the problem is cropping
up. I've checked the References screen on the VBA form, and there's no
broken library references.

Any suggestions or comments? I'm at a loss at this point.

Thanks!

Dennis

 

[prabha]

Hi Dennis,

Have looked into re-registering DAO360.dll on the problem machine?

Click Start > Run
Type
regsvr32 "full path to file DAO360.dll"
Click OK

I hope this helps! If you have additional questions on this topic, please
respond back to this posting.


Regards,

Eric Butts
Microsoft Access Support

"Microsoft Security Announcement: Have you installed the patch for
Microsoft Security Bulletin MS03-026? If not Microsoft strongly advises
you to review the information at the following link regarding Microsoft
Security Bulletin MS03-026
<http://www.microsoft.com/security/security_bulletins/ms03-026.asp> and/or
to visit Windows Update at <http://windowsupdate.microsoft.com/> to install
the patch. Running the SCAN program from the Windows Update site will help
to insure you are current with all security patches, not just MS03-026."


--------------------
| From: "Dennis Snelgrove" <[email protected]>
| Subject: Getting #ERROR# in subform
| Date: Mon, 9 Feb 2004 12:31:22 -0500
| Lines: 23
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <[email protected]>
| Newsgroups: microsoft.public.access.forms,microsoft.public.access.queries
| NNTP-Posting-Host: m119-85.on.tac.net 209.202.119.85
| Path:
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!cpmsftngxa09.phx.gbl!TK2MSFTNGP08.
phx.gbl!TK2MSFTNGP10.phx.gbl
| Xref: cpmsftngxa07.phx.gbl microsoft.public.access.queries:189153
microsoft.public.access.forms:254386
| X-Tomcat-NG: microsoft.public.access.forms
|
| I've got a front-end that I'm running on 5 different PCs in our office.
One
| of the forms has a continuous subform with a textbox that shows the
| formatted time, and this is a calculated field from the form's
recordsource
| query. On 4 of the 5 PCs, the subform works perfectly; on the 5th I get
| nothing but "#ERROR#" in the time textbox. All the rest of the form works
| perfectly, though. The first record in the subform shows the proper time,
| the rest show "#ERROR#", and if we scroll the subform at all, that first
| record also goes to "#ERROR#".
|
| I've checked that the front-end is the same as the other 4 PCs, and it is.
| I've checked the Regional Settings, and they're no different. I've run the
| source query itself and the output is proper for the entire recordset;
it's
| just when the recordset is fed to the subform that the problem is cropping
| up. I've checked the References screen on the VBA form, and there's no
| broken library references.
|
| Any suggestions or comments? I'm at a loss at this point.
|
| Thanks!
|
| Dennis
|
|
|

 

[[MVP] S.Clark]

My guess was to check the references. Double check them one more time.

What is the source/calculation/expression of the problem field?

--
HTH,

Steve Clark, Access MVP
FMS, Inc.
Professional Solutions Group
http://www.FMSInc.com
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Is your Access database too slow?
Are you ready to upgrade to SQL Server?
Contact us for optimization and/or upsizing!
http://www.FMSInc.com/consulting
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

[Dennis Snelgrove]

Unfortunately, this didn't do any good. I'm at a loss at this point.

What exactly was I accomplishing by registering the dll? Any links to
explain it?