coding stopped working???

J

Jacco

Hi everyone, I coded some VB for a report that used to work fine. Now I
changed from Access 2000 to 2003 (and different computer) and now the output
results into #name?

The code: (shorted due to repeating simular actions)

Option Compare Database
Option Explicit
Public DurationSum As Double
Public DurationPage As Double

Private Sub Detail_Print(Cancel As Integer, FormatCount As Integer)
DurationSum = DurationSum + Reports![Jar_Jeppesen_L]![Duration]
DurationPage = DurationPage + Reports![Jar_Jeppesen_L]![Duration]
End Sub

Private Sub PageHeaderSection_Format(Cancel As Integer, FormatCount As
Integer)
' reset the counter for each new page
DurationPage = 0
End Sub

The output field(s):
=IIf([DurationPage]=0,"",Int([DurationPage]))
etc.

Any help is appreciated.
Jacco
 
T

Tino Faeustel

Hallo,

i dont know, what's the problem with Access2003, but if i have to do such
calculations i do not use direct access to the variables; i use a function
instead :

Function GetDurationPage As Double
GetDurationPage = DurationPage
end function

The output field(s) sould look like:
=IIf(DurationPage()=0,"",Int(DurationPage()))

But it seems to be the same ...
 
J

John Spencer (MVP)

To do its job, Access (like most modern programs) makes use of various external
program and object libraries that provide functionality that may be shared among
applications. For example, Access always uses the Visual Basic for Applications
library, the version-appropriate Access Object Library, and the OLE Automation
library. References to the specific library files, including their locations,
are stored with your database. But these library modules may not be in the same
location on different machines, especially if they have different versions of
Microsoft Office. If you move a database from one machine to another, these
references may be "broken"; that is, one or more of the library files may not
be where the stored reference says it is.

When this happens, you need to take steps to let Access repair the broken
reference(s) ON THE COMPUTER WHERE THE FAILURE IS OCCURING.

Here are MVP Doug Steele's instructions for how to do it:

*** Quote ***

Any time functions that previously worked suddenly don't, the first thing to
suspect is a references problem.

This can be caused by differences in either the location or file version of
certain files between the machine where the application was developed, and where
it's being run (or the file missing completely from the target machine). Such
differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug window
on top" option). Select Tools | References from the menu bar. Examine all of the
selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you just
unselected (you can tell by doing a Compile All Modules), go back in and
reselect them.

If none have "MISSING:", select an additional reference at random, back out of
the dialog, then go back in and unselect the reference you just added. If that
doesn't solve the problem, try to unselect as many of the selected references as
you can (Access may not let you unselect them all), back out of the dialog, then
go back in and reselect the references you just unselected. (NOTE: write down
what the references are before you delete them, because they'll be in a
different order when you go back in)

For far more than you could ever want to know about this problem, check out
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

Just so you know: the problem will occur even if the library that contains the
specific function that's failing doesn't have a problem.

**** End Quote ****

So, follow those instructions and see if your problem goes away.

Check out the following reference
http://www.trigeminal.com/usenet/usenet026.asp?1036
 
J

Jacco

John Spencer (MVP) said:
To do its job, Access (like most modern programs) makes use of various
external
program and object libraries that provide functionality that may be shared
among
applications. For example, Access always uses the Visual Basic for
Applications
library, the version-appropriate Access Object Library, and the OLE
Automation
library. References to the specific library files, including their
locations,
are stored with your database. But these library modules may not be in
the same
location on different machines, especially if they have different versions
of
Microsoft Office. If you move a database from one machine to another,
these
references may be "broken"; that is, one or more of the library files may
not
be where the stored reference says it is.

When this happens, you need to take steps to let Access repair the broken
reference(s) ON THE COMPUTER WHERE THE FAILURE IS OCCURING.

Here are MVP Doug Steele's instructions for how to do it:

*** Quote ***

Any time functions that previously worked suddenly don't, the first thing
to
suspect is a references problem.

This can be caused by differences in either the location or file version
of
certain files between the machine where the application was developed, and
where
it's being run (or the file missing completely from the target machine).
Such
differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open
the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window
on top" option). Select Tools | References from the menu bar. Examine all
of the
selected references.

If any of the selected references have "MISSING:" in front of them,
unselect
them, and back out of the dialog. If you really need the reference(s) you
just
unselected (you can tell by doing a Compile All Modules), go back in and
reselect them.

If none have "MISSING:", select an additional reference at random, back
out of
the dialog, then go back in and unselect the reference you just added. If
that
doesn't solve the problem, try to unselect as many of the selected
references as
you can (Access may not let you unselect them all), back out of the
dialog, then
go back in and reselect the references you just unselected. (NOTE: write
down
what the references are before you delete them, because they'll be in a
different order when you go back in)

For far more than you could ever want to know about this problem, check
out
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

Just so you know: the problem will occur even if the library that contains
the
specific function that's failing doesn't have a problem.

**** End Quote ****

So, follow those instructions and see if your problem goes away.

Check out the following reference
http://www.trigeminal.com/usenet/usenet026.asp?1036
Click to expand...

That didn't help. Since it's only short code.... better to just rewrite
it???? or is the code just invalid now?????
 
J

John Spencer (MVP)

Don't know. I guess you could try it.

Do you have any other problems with the database?
 
J

Jacco

Not yet. It is only a small conversion with a couple of linked tables. I
only use it to print out a report.
 
J

Jacco

OOOPS... some security setting changed... I was on medium, so I blocked my
own coding.... SOLVED!!!!!!!!
 
Top