Re: Error 3220 - Function Is Not Available In Expression In Table Level Validation Expression
OK I see where you are coming from. Please explain one thing to me, I have
set up 2 clean machines ie fresh installations of Windows XP And 98 all that
is on the machines are the operating systems. I then Install my app which
also installs Access 2002 Runtime. All the files mentioned in the Reference
list do get installed.
On 98 I run OSP.MSI once this is done The app runs perfectly.
On XP OSP.MSI will not run (which is quite normal) I go and run the app and
before clicking the button that causes the error, I open C:\Program
Files\Common Files\Microsoft Shared\MSInfo\M SInfo32.exe. I then point to
ACCESS--> Summary and it tells me that Access Is Not Installed. I Press F5 a
few times, then it shows me the Access "Installati on". I then go back to my
App click the button (which is on a logon form) and the app works - at this
point I can no longer simulate the error (i.e the application runs perfectly
from here on). Have you got any idea what is happening. I know this sounds
ridiculous but it is the case.
Steve
"Michael (michka) Kaplan [MS]" <michkap@online .microsoft.com> wrote in
message news:40c493cf$1 @news.microsoft .com...[color=blue]
> Ok, my guess is that at least one (and maybe several) of these libraries[/color]
are[color=blue]
> in a different location on the machines where the failure occurs. For some
> reason, the Jet ES does not do the fixup properly in this case, so you[/color]
need[color=blue]
> to make sure you do the reference fixup in VBA first (by referencing these
> objects in a procedure that gets called before that table is used).
>
>
> --
> MichKa [MS]
> NLS Collation/Locale/Keyboard Development
> Globalization Infrastructure and Font Technologies
>
> This posting is provided "AS IS" with
> no warranties, and confers no rights.
>
>
> "Steve" <stevej@ufrmsa1 .uniforum.org.z a> wrote in message
> news:ca1q74$6ok $1@ctb-nnrp2.saix.net. ..[color=green]
> > OK I AM WRONG
> >
> > References Used
> >
> > C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6 \vbe6.dll
> > C:\Program Files\Microsoft Office\Office10 \msacc.olb
> >
> > C:\Program Files\ Common Files\Microsoft Shared\DAO\dao3 60.dll
> >
> > C:\Windows\Syst em32\stdole2.tl b
> >
> > C:\Program Files\Microsoft Office\Office10 \mscal.ocx
> >
> > C:\Windows\Syst em32\Inetsrv\cn fgprts.ocx
> >
> > C:\Windows\Syst em32\mscomm32.o cx
> >
> > C:\Windows\Syst em32\smsmsg.ocx - This is an ocx I use to send and[/color][/color]
receive[color=blue][color=green]
> > SMS's
> >
> >
> >
> > Steve
> >
> > "Michael (michka) Kaplan [MS]" <michkap@online .microsoft.com> wrote in
> > message news:40c3273d$1 @news.microsoft .com...[color=darkred]
> > > Your behavior exactly matches the circumstances I mention below. SO,[/color][/color][/color]
if[color=blue][color=green]
> > you[color=darkred]
> > > would like to solve the problem:
> > >
> > > 1) ASSUME YOU ARE WRONG.
> > >
> > > 2) List your exact references in your response to this message --[/color]
> > including[color=darkred]
> > > the drive/dir location of each typelib (DLL, OCX, TLB)
> > >
> > > 3) Try what I asked you to do.
> > >
> > > All three steps are important for you to try if you truly want to[/color][/color][/color]
solve[color=blue][color=green]
> > the[color=darkred]
> > > problem. If, on the other hand, you want to keep spinning your wheels[/color][/color]
> and[color=green][color=darkred]
> > > having a problem, then proceed as you are doing now.
> > >
> > >
> > > --
> > > MichKa [MS]
> > > NLS Collation/Locale/Keyboard Development
> > > Globalization Infrastructure and Font Technologies
> > >
> > > This posting is provided "AS IS" with
> > > no warranties, and confers no rights.
> > >
> > >
> > > "Steve" <stevej@ufrmsa1 .uniforum.org.z a> wrote in message
> > > news:c9ulio$t8t $2@ctb-nnrp2.saix.net. ..
> > > > The references are definately OK, I have checked versions against
> > > > installation versions and unregistered and reregisterd
> > > > them all.
> > > >
> > > > Remember I get the same error when manually inserting a value into[/color][/color][/color]
the[color=blue][color=green][color=darkred]
> > > table
> > > > i.e opening the table and typing in a record,
> > > > the first time I get the error, the second time the record is[/color][/color]
> inserted.[color=green]
> > I[color=darkred]
> > > > have also compacted and repaired the database to no availe.
> > > >
> > > > As I said in the origional question this is really a weird problem.
> > > >
> > > > I'm starting to think it has something to do with the auto number.
> > > >
> > > > Steve
> > > >
> > > > "Michael (michka) Kaplan [MS]" <michkap@online .microsoft.com> wrote[/color][/color][/color]
in[color=blue][color=green][color=darkred]
> > > > message news:40c26708$1 @news.microsoft .com...
> > > > > And if you take out the function calls? You might want to humor me[/color][/color]
> and[color=green][color=darkred]
> > > try
> > > > > it, just for giggles....
> > > > >
> > > > > Out of curiousity, what are the references?
> > > > >
> > > > > There is an interesting case where even if all the references are[/color][/color]
> okay[color=green][color=darkred]
> > > > that
> > > > > a changed path of one of the references typelibs (DLL, OCX, or[/color][/color][/color]
TLB)[color=blue][color=green]
> > can[color=darkred]
> > > > > cause a partial reference break because the reference fixup does[/color][/color][/color]
not[color=blue][color=green][color=darkred]
> > > > happen
> > > > > properly when the ES is doing the fixup as opposed to VBA doing it
> > > > directly.
> > > > > The workaround (if this is the problem) is to make sure that the
> > > > references
> > > > > are all disambiguated and loaded prior to being used.
> > > > >
> > > > >
> > > > > --
> > > > > MichKa [MS]
> > > > > NLS Collation/Locale/Keyboard Development
> > > > > Globalization Infrastructure and Font Technologies
> > > > >
> > > > > This posting is provided "AS IS" with
> > > > > no warranties, and confers no rights.
> > > > >
> > > > >
> > > > > "Steve" <stevej@ufrmsa1 .uniforum.org.z a> wrote in message
> > > > > news:c9tdrm$hh5 $2@ctb-nnrp2.saix.net. ..
> > > > > > I think you are correct, but the problem is I have checked out[/color][/color][/color]
my[color=blue][color=green][color=darkred]
> > > > > References
> > > > > > and everything seems to be in order.
> > > > > >
> > > > > > Steve
> > > > > >
> > > > > > "Michael (michka) Kaplan [MS]" <michkap@online .microsoft.com>[/color][/color]
> wrote[color=green]
> > in[color=darkred]
> > > > > > message news:40c23215$1 @news.microsoft .com...
> > > > > > > If I had to guess I would guess that it is complaining about[/color][/color][/color]
one[color=blue][color=green]
> > of[color=darkred]
> > > > the
> > > > > > > function calls like Time().
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > MichKa [MS]
> > > > > > > NLS Collation/Locale/Keyboard Development
> > > > > > > Globalization Infrastructure and Font Technologies
> > > > > > >
> > > > > > > This posting is provided "AS IS" with
> > > > > > > no warranties, and confers no rights.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >[/color]
> >
> >[/color]
>
>[/color]
OK I see where you are coming from. Please explain one thing to me, I have
set up 2 clean machines ie fresh installations of Windows XP And 98 all that
is on the machines are the operating systems. I then Install my app which
also installs Access 2002 Runtime. All the files mentioned in the Reference
list do get installed.
On 98 I run OSP.MSI once this is done The app runs perfectly.
On XP OSP.MSI will not run (which is quite normal) I go and run the app and
before clicking the button that causes the error, I open C:\Program
Files\Common Files\Microsoft Shared\MSInfo\M SInfo32.exe. I then point to
ACCESS--> Summary and it tells me that Access Is Not Installed. I Press F5 a
few times, then it shows me the Access "Installati on". I then go back to my
App click the button (which is on a logon form) and the app works - at this
point I can no longer simulate the error (i.e the application runs perfectly
from here on). Have you got any idea what is happening. I know this sounds
ridiculous but it is the case.
Steve
"Michael (michka) Kaplan [MS]" <michkap@online .microsoft.com> wrote in
message news:40c493cf$1 @news.microsoft .com...[color=blue]
> Ok, my guess is that at least one (and maybe several) of these libraries[/color]
are[color=blue]
> in a different location on the machines where the failure occurs. For some
> reason, the Jet ES does not do the fixup properly in this case, so you[/color]
need[color=blue]
> to make sure you do the reference fixup in VBA first (by referencing these
> objects in a procedure that gets called before that table is used).
>
>
> --
> MichKa [MS]
> NLS Collation/Locale/Keyboard Development
> Globalization Infrastructure and Font Technologies
>
> This posting is provided "AS IS" with
> no warranties, and confers no rights.
>
>
> "Steve" <stevej@ufrmsa1 .uniforum.org.z a> wrote in message
> news:ca1q74$6ok $1@ctb-nnrp2.saix.net. ..[color=green]
> > OK I AM WRONG
> >
> > References Used
> >
> > C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6 \vbe6.dll
> > C:\Program Files\Microsoft Office\Office10 \msacc.olb
> >
> > C:\Program Files\ Common Files\Microsoft Shared\DAO\dao3 60.dll
> >
> > C:\Windows\Syst em32\stdole2.tl b
> >
> > C:\Program Files\Microsoft Office\Office10 \mscal.ocx
> >
> > C:\Windows\Syst em32\Inetsrv\cn fgprts.ocx
> >
> > C:\Windows\Syst em32\mscomm32.o cx
> >
> > C:\Windows\Syst em32\smsmsg.ocx - This is an ocx I use to send and[/color][/color]
receive[color=blue][color=green]
> > SMS's
> >
> >
> >
> > Steve
> >
> > "Michael (michka) Kaplan [MS]" <michkap@online .microsoft.com> wrote in
> > message news:40c3273d$1 @news.microsoft .com...[color=darkred]
> > > Your behavior exactly matches the circumstances I mention below. SO,[/color][/color][/color]
if[color=blue][color=green]
> > you[color=darkred]
> > > would like to solve the problem:
> > >
> > > 1) ASSUME YOU ARE WRONG.
> > >
> > > 2) List your exact references in your response to this message --[/color]
> > including[color=darkred]
> > > the drive/dir location of each typelib (DLL, OCX, TLB)
> > >
> > > 3) Try what I asked you to do.
> > >
> > > All three steps are important for you to try if you truly want to[/color][/color][/color]
solve[color=blue][color=green]
> > the[color=darkred]
> > > problem. If, on the other hand, you want to keep spinning your wheels[/color][/color]
> and[color=green][color=darkred]
> > > having a problem, then proceed as you are doing now.
> > >
> > >
> > > --
> > > MichKa [MS]
> > > NLS Collation/Locale/Keyboard Development
> > > Globalization Infrastructure and Font Technologies
> > >
> > > This posting is provided "AS IS" with
> > > no warranties, and confers no rights.
> > >
> > >
> > > "Steve" <stevej@ufrmsa1 .uniforum.org.z a> wrote in message
> > > news:c9ulio$t8t $2@ctb-nnrp2.saix.net. ..
> > > > The references are definately OK, I have checked versions against
> > > > installation versions and unregistered and reregisterd
> > > > them all.
> > > >
> > > > Remember I get the same error when manually inserting a value into[/color][/color][/color]
the[color=blue][color=green][color=darkred]
> > > table
> > > > i.e opening the table and typing in a record,
> > > > the first time I get the error, the second time the record is[/color][/color]
> inserted.[color=green]
> > I[color=darkred]
> > > > have also compacted and repaired the database to no availe.
> > > >
> > > > As I said in the origional question this is really a weird problem.
> > > >
> > > > I'm starting to think it has something to do with the auto number.
> > > >
> > > > Steve
> > > >
> > > > "Michael (michka) Kaplan [MS]" <michkap@online .microsoft.com> wrote[/color][/color][/color]
in[color=blue][color=green][color=darkred]
> > > > message news:40c26708$1 @news.microsoft .com...
> > > > > And if you take out the function calls? You might want to humor me[/color][/color]
> and[color=green][color=darkred]
> > > try
> > > > > it, just for giggles....
> > > > >
> > > > > Out of curiousity, what are the references?
> > > > >
> > > > > There is an interesting case where even if all the references are[/color][/color]
> okay[color=green][color=darkred]
> > > > that
> > > > > a changed path of one of the references typelibs (DLL, OCX, or[/color][/color][/color]
TLB)[color=blue][color=green]
> > can[color=darkred]
> > > > > cause a partial reference break because the reference fixup does[/color][/color][/color]
not[color=blue][color=green][color=darkred]
> > > > happen
> > > > > properly when the ES is doing the fixup as opposed to VBA doing it
> > > > directly.
> > > > > The workaround (if this is the problem) is to make sure that the
> > > > references
> > > > > are all disambiguated and loaded prior to being used.
> > > > >
> > > > >
> > > > > --
> > > > > MichKa [MS]
> > > > > NLS Collation/Locale/Keyboard Development
> > > > > Globalization Infrastructure and Font Technologies
> > > > >
> > > > > This posting is provided "AS IS" with
> > > > > no warranties, and confers no rights.
> > > > >
> > > > >
> > > > > "Steve" <stevej@ufrmsa1 .uniforum.org.z a> wrote in message
> > > > > news:c9tdrm$hh5 $2@ctb-nnrp2.saix.net. ..
> > > > > > I think you are correct, but the problem is I have checked out[/color][/color][/color]
my[color=blue][color=green][color=darkred]
> > > > > References
> > > > > > and everything seems to be in order.
> > > > > >
> > > > > > Steve
> > > > > >
> > > > > > "Michael (michka) Kaplan [MS]" <michkap@online .microsoft.com>[/color][/color]
> wrote[color=green]
> > in[color=darkred]
> > > > > > message news:40c23215$1 @news.microsoft .com...
> > > > > > > If I had to guess I would guess that it is complaining about[/color][/color][/color]
one[color=blue][color=green]
> > of[color=darkred]
> > > > the
> > > > > > > function calls like Time().
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > MichKa [MS]
> > > > > > > NLS Collation/Locale/Keyboard Development
> > > > > > > Globalization Infrastructure and Font Technologies
> > > > > > >
> > > > > > > This posting is provided "AS IS" with
> > > > > > > no warranties, and confers no rights.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >[/color]
> >
> >[/color]
>
>[/color]
Comment