By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,109 Members | 932 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,109 IT Pros & Developers. It's quick & easy.

Error 3220 - Function Is Not Available In Expression In Table Level Validation Expression

P: n/a
Hi

I have a really weird problem and any assistance would be welcome.

I have developed an app in Access 2002. The app runs perfectly on the
development machine. I have packaged the app
using the Microsoft XP Developer Packaging Wizard (Service Pack 1). The 1st
3 releases of the app ran perfectly on
site.

On Friday the 4th release of the app went out to a customer. The app opened
perfectly but on clicking OK on my login form
I get the error : 3220 - The functiom is not available in expression in
table level validation expression.

I took the 2 main files one mde file containing the application and an mdb
file containing the data which is linked into the
mde file from the support directory on the installation CD and copied them
to a machine which has Office XP Professional
loaded (as I can not simulate the error on the box used for development). I
found that when I went into a table that when
manually entering a record I got the same error, the weird part is neither
the table nor the code populating the table
has changed since the 1st release of the app (In fact it is code I use for a
table and module that I use in many other
applications).

The table layout is as follows :

Key AutoNumber Primary Key
UserName Text(15) Mandatory
No Default Value
SecurityLevel Long Integer Mandatory
Default Value 0
DBChanged Text(20) Mandatory
No Default Value
RecordChanged Text(100) Mandatory
No Default Value
DBAction Text(100) Mandatory
No Default Value
DateChanged Date/Time Mandatory
Default Value Date()
TimeChanged Date/Time Mandatory
Default Value Time()
TillNo Integer
Default Value 0
The code used to populate the table is as follows :

Sub logchg(tbl As String, rec As Variant, action As String)
Dim srec As String
Dim logrs As Recordset

srec = CStr(rec)

Set logrs = db.OpenRecordset("tblLog")
logrs.AddNew
logrs![UserName] = modGlobals.user
logrs![SecurityLevel] = modGlobals.SecurityLevel
logrs![DbChanged] = tbl
logrs![RecordChanged] = srec
logrs![DBAction] = action
logrs![TillNo] = modGlobals.TillNo
logrs.Update
logrs.Close
End Sub

The call that causes the error is :

Call modSecurity.logchg("N/A", "N/A", "LOGON")

Can anyone explain why I get the error ?

TIA
Steve
Nov 13 '05 #1
Share this Question
Share on Google+
18 Replies


P: n/a
Steve wrote:
Hi

I have a really weird problem and any assistance would be welcome.

I have developed an app in Access 2002. The app runs perfectly on the
development machine. I have packaged the app
using the Microsoft XP Developer Packaging Wizard (Service Pack 1). The 1st
3 releases of the app ran perfectly on
site.

On Friday the 4th release of the app went out to a customer. The app opened
perfectly but on clicking OK on my login form
I get the error : 3220 - The functiom is not available in expression in
table level validation expression.

I took the 2 main files one mde file containing the application and an mdb
file containing the data which is linked into the
mde file from the support directory on the installation CD and copied them
to a machine which has Office XP Professional
loaded (as I can not simulate the error on the box used for development). I
found that when I went into a table that when
manually entering a record I got the same error, the weird part is neither
the table nor the code populating the table
has changed since the 1st release of the app (In fact it is code I use for a
table and module that I use in many other
applications).

The table layout is as follows :

Key AutoNumber Primary Key
UserName Text(15) Mandatory
No Default Value
SecurityLevel Long Integer Mandatory
Default Value 0
DBChanged Text(20) Mandatory
No Default Value
RecordChanged Text(100) Mandatory
No Default Value
DBAction Text(100) Mandatory
No Default Value
DateChanged Date/Time Mandatory
Default Value Date()
TimeChanged Date/Time Mandatory
Default Value Time()
TillNo Integer
Default Value 0
The code used to populate the table is as follows :

Sub logchg(tbl As String, rec As Variant, action As String)
Dim srec As String
Dim logrs As Recordset

srec = CStr(rec)

Set logrs = db.OpenRecordset("tblLog")
logrs.AddNew
logrs![UserName] = modGlobals.user
logrs![SecurityLevel] = modGlobals.SecurityLevel
logrs![DbChanged] = tbl
logrs![RecordChanged] = srec
logrs![DBAction] = action
logrs![TillNo] = modGlobals.TillNo
logrs.Update
logrs.Close
End Sub

The call that causes the error is :

Call modSecurity.logchg("N/A", "N/A", "LOGON")

Can anyone explain why I get the error ?

TIA
Steve


I have A97, and error 3220 referes to Paradox and 2426 is Function isn't
available in expressions. Your error has the addendum of
TableLevelValidation to my 2426.

Open up your table tblLog. Do you have a validation rule on any of the
fields you are updating? Maybe make a copy of the current log table and
then open the log file and remove any validation rules and text of so.

If that doesn't help, is there a way to verify what line in LogChg that
blows up? IOW, step through code and locate which field you are
updating that is the cause of the problem.


Nov 13 '05 #2

P: n/a

"Salad" <oi*@vinegar.com> wrote in message
news:Ds******************@newsread1.news.pas.earth link.net...
Steve wrote:
Hi

I have a really weird problem and any assistance would be welcome.

I have developed an app in Access 2002. The app runs perfectly on the
development machine. I have packaged the app
using the Microsoft XP Developer Packaging Wizard (Service Pack 1). The 1st 3 releases of the app ran perfectly on
site.

On Friday the 4th release of the app went out to a customer. The app opened perfectly but on clicking OK on my login form
I get the error : 3220 - The functiom is not available in expression in
table level validation expression.

I took the 2 main files one mde file containing the application and an mdb file containing the data which is linked into the
mde file from the support directory on the installation CD and copied them to a machine which has Office XP Professional
loaded (as I can not simulate the error on the box used for development). I found that when I went into a table that when
manually entering a record I got the same error, the weird part is neither the table nor the code populating the table
has changed since the 1st release of the app (In fact it is code I use for a table and module that I use in many other
applications).

The table layout is as follows :

Key AutoNumber Primary Key
UserName Text(15) Mandatory No Default Value
SecurityLevel Long Integer Mandatory Default Value 0
DBChanged Text(20) Mandatory No Default Value
RecordChanged Text(100) Mandatory
No Default Value
DBAction Text(100) Mandatory No Default Value
DateChanged Date/Time Mandatory Default Value Date()
TimeChanged Date/Time Mandatory Default Value Time()
TillNo Integer
Default Value 0
The code used to populate the table is as follows :

Sub logchg(tbl As String, rec As Variant, action As String)
Dim srec As String
Dim logrs As Recordset

srec = CStr(rec)

Set logrs = db.OpenRecordset("tblLog")
logrs.AddNew
logrs![UserName] = modGlobals.user
logrs![SecurityLevel] = modGlobals.SecurityLevel
logrs![DbChanged] = tbl
logrs![RecordChanged] = srec
logrs![DBAction] = action
logrs![TillNo] = modGlobals.TillNo
logrs.Update
logrs.Close
End Sub

The call that causes the error is :

Call modSecurity.logchg("N/A", "N/A", "LOGON")

Can anyone explain why I get the error ?

TIA
Steve


I have A97, and error 3220 referes to Paradox and 2426 is Function isn't
available in expressions. Your error has the addendum of
TableLevelValidation to my 2426.

Open up your table tblLog. Do you have a validation rule on any of the
fields you are updating? Maybe make a copy of the current log table and
then open the log file and remove any validation rules and text of so.

If that doesn't help, is there a way to verify what line in LogChg that
blows up? IOW, step through code and locate which field you are
updating that is the cause of the problem.

Thanks for the response, I have no validation rule set up, and the code
seems to crash on :

logrs.Update

which unfortunately tells me nothing.

Steve
Nov 13 '05 #3

P: n/a
Steve wrote:
I have A97, and error 3220 referes to Paradox and 2426 is Function isn't
available in expressions. Your error has the addendum of
TableLevelValidation to my 2426.

Open up your table tblLog. Do you have a validation rule on any of the
fields you are updating? Maybe make a copy of the current log table and
then open the log file and remove any validation rules and text of so.

If that doesn't help, is there a way to verify what line in LogChg that
blows up? IOW, step through code and locate which field you are
updating that is the cause of the problem.

Thanks for the response, I have no validation rule set up, and the code
seems to crash on :

logrs.Update

which unfortunately tells me nothing.

Steve


OK. You know the line. It is telling you there is a value it doesn't
like...near as I can tell. I'll assume you know how to step through
code. If not, click on the bar to the left of the AddNew line that puts
a dot on the bar and highlights the line. Now run the process. Check
the values of each item you are updating in the recordset.

ALso, copy the code and put into a module. Instead of plugging in the
values in the program, attempt to add with valid values. Ex:
logrs![UserName] = "Steve"
Do that for all fields. If you can't add a record with
plugged-in-manually and the values are correct for the field, maybe you
have an existing record that conflicts with something.

When are you calling this? I had a main form that called some functions
and queries that used NZ() and otherthings like that. Once the form was
loaded the functions I was using could be used. But on the loading of
the form, the VBA functions were not available.

I doubt that is the case if you have been using this method for a while.
Check your data.

If you can add a record with manual data and the data looks ok when you
step through code, then start commenting out a line where you update the
recordset and keep commenting out an update line until you know which
one goofs up. Ex:
logrs![UserName] = "Steve"
and it blows up. Comment out
'logrs![UserName] = "Steve"
and it doesn't blow up. That means there is something wrong with the
UserName field in the table or else Steve is not a valid value.

Trial and error may be the easies method to find out what is wrong.

Nov 13 '05 #4

P: n/a
If I had to guess I would guess that it is complaining about one of 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.

Nov 13 '05 #5

P: n/a

"Salad" <oi*@vinegar.com> wrote in message
news:yU*******************@newsread1.news.pas.eart hlink.net...
Steve wrote:
I have A97, and error 3220 referes to Paradox and 2426 is Function isn't
available in expressions. Your error has the addendum of
TableLevelValidation to my 2426.

Open up your table tblLog. Do you have a validation rule on any of the
fields you are updating? Maybe make a copy of the current log table and
then open the log file and remove any validation rules and text of so.

If that doesn't help, is there a way to verify what line in LogChg that
blows up? IOW, step through code and locate which field you are
updating that is the cause of the problem.

Thanks for the response, I have no validation rule set up, and the code
seems to crash on :

logrs.Update

which unfortunately tells me nothing.

Steve


OK. You know the line. It is telling you there is a value it doesn't
like...near as I can tell. I'll assume you know how to step through
code. If not, click on the bar to the left of the AddNew line that puts
a dot on the bar and highlights the line. Now run the process. Check
the values of each item you are updating in the recordset.

ALso, copy the code and put into a module. Instead of plugging in the
values in the program, attempt to add with valid values. Ex:
logrs![UserName] = "Steve"
Do that for all fields. If you can't add a record with
plugged-in-manually and the values are correct for the field, maybe you
have an existing record that conflicts with something.

When are you calling this? I had a main form that called some functions
and queries that used NZ() and otherthings like that. Once the form was
loaded the functions I was using could be used. But on the loading of
the form, the VBA functions were not available.

I doubt that is the case if you have been using this method for a while.
Check your data.

If you can add a record with manual data and the data looks ok when you
step through code, then start commenting out a line where you update the
recordset and keep commenting out an update line until you know which
one goofs up. Ex:
logrs![UserName] = "Steve"
and it blows up. Comment out
'logrs![UserName] = "Steve"
and it doesn't blow up. That means there is something wrong with the
UserName field in the table or else Steve is not a valid value.

Trial and error may be the easies method to find out what is wrong.


Thanks, but I have tried what you are telling me.

Steve
Nov 13 '05 #6

P: n/a
I think you are correct, but the problem is I have checked out my References
and everything seems to be in order.

Steve

"Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
If I had to guess I would guess that it is complaining about one of 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.

Nov 13 '05 #7

P: n/a
And if you take out the function calls? You might want to humor me and try
it, just for giggles....

Out of curiousity, what are the references?

There is an interesting case where even if all the references are okay that
a changed path of one of the references typelibs (DLL, OCX, or TLB) can
cause a partial reference break because the reference fixup does not 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" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:c9**********@ctb-nnrp2.saix.net...
I think you are correct, but the problem is I have checked out my References and everything seems to be in order.

Steve

"Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
If I had to guess I would guess that it is complaining about one of 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.


Nov 13 '05 #8

P: n/a
> I think you are correct, but the problem is I have checked out my
References
and everything seems to be in order.


I've experienced similar errors (function not available...) and it turned
out to be a references issue. Checking the version and path of the
different ocx and dll files and comparing between development and client
machines is a logical troubleshooting step. You might try removing all
references (on the client machine), closing out of Access, and then going
back in and adding them all back.

Just my two cents...
Nov 13 '05 #9

P: n/a
Thanks the help is appreciated.

Steve

"deko" <no****@hotmail.com> wrote in message
news:r7*******************@newssvr29.news.prodigy. com...
I think you are correct, but the problem is I have checked out my

References
and everything seems to be in order.


I've experienced similar errors (function not available...) and it turned
out to be a references issue. Checking the version and path of the
different ocx and dll files and comparing between development and client
machines is a logical troubleshooting step. You might try removing all
references (on the client machine), closing out of Access, and then going
back in and adding them all back.

Just my two cents...

Nov 13 '05 #10

P: n/a
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 the table
i.e opening the table and typing in a record,
the first time I get the error, the second time the record is inserted. I
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]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
And if you take out the function calls? You might want to humor me and try
it, just for giggles....

Out of curiousity, what are the references?

There is an interesting case where even if all the references are okay that a changed path of one of the references typelibs (DLL, OCX, or TLB) can
cause a partial reference break because the reference fixup does not 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" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:c9**********@ctb-nnrp2.saix.net...
I think you are correct, but the problem is I have checked out my

References
and everything seems to be in order.

Steve

"Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
If I had to guess I would guess that it is complaining about one of 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.



Nov 13 '05 #11

P: n/a
Your behavior exactly matches the circumstances I mention below. SO, if you
would like to solve the problem:

1) ASSUME YOU ARE WRONG.

2) List your exact references in your response to this message -- including
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 solve the
problem. If, on the other hand, you want to keep spinning your wheels and
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" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:c9**********@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 the table i.e opening the table and typing in a record,
the first time I get the error, the second time the record is inserted. I
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]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
And if you take out the function calls? You might want to humor me and try
it, just for giggles....

Out of curiousity, what are the references?

There is an interesting case where even if all the references are okay

that
a changed path of one of the references typelibs (DLL, OCX, or TLB) can
cause a partial reference break because the reference fixup does not

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" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:c9**********@ctb-nnrp2.saix.net...
I think you are correct, but the problem is I have checked out my

References
and everything seems to be in order.

Steve

"Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
> If I had to guess I would guess that it is complaining about one of

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.
>
>
>



Nov 13 '05 #12

P: n/a
I think I've found the problem (and it looks like I caused it). I have both
office 97 ode tools and XP Developer on the same machine - according to
Microsoft this can cause a problem.

Thanks for all the assistance

Steve

"Steve" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:c9**********@ctb-nnrp2.saix.net...
Hi

I have a really weird problem and any assistance would be welcome.

I have developed an app in Access 2002. The app runs perfectly on the
development machine. I have packaged the app
using the Microsoft XP Developer Packaging Wizard (Service Pack 1). The 1st 3 releases of the app ran perfectly on
site.

On Friday the 4th release of the app went out to a customer. The app opened perfectly but on clicking OK on my login form
I get the error : 3220 - The functiom is not available in expression in
table level validation expression.

I took the 2 main files one mde file containing the application and an mdb
file containing the data which is linked into the
mde file from the support directory on the installation CD and copied them
to a machine which has Office XP Professional
loaded (as I can not simulate the error on the box used for development). I found that when I went into a table that when
manually entering a record I got the same error, the weird part is neither
the table nor the code populating the table
has changed since the 1st release of the app (In fact it is code I use for a table and module that I use in many other
applications).

The table layout is as follows :

Key AutoNumber Primary Key
UserName Text(15) Mandatory No Default Value
SecurityLevel Long Integer Mandatory
Default Value 0
DBChanged Text(20) Mandatory
No Default Value
RecordChanged Text(100) Mandatory
No Default Value
DBAction Text(100) Mandatory No Default Value
DateChanged Date/Time Mandatory
Default Value Date()
TimeChanged Date/Time Mandatory
Default Value Time()
TillNo Integer
Default Value 0
The code used to populate the table is as follows :

Sub logchg(tbl As String, rec As Variant, action As String)
Dim srec As String
Dim logrs As Recordset

srec = CStr(rec)

Set logrs = db.OpenRecordset("tblLog")
logrs.AddNew
logrs![UserName] = modGlobals.user
logrs![SecurityLevel] = modGlobals.SecurityLevel
logrs![DbChanged] = tbl
logrs![RecordChanged] = srec
logrs![DBAction] = action
logrs![TillNo] = modGlobals.TillNo
logrs.Update
logrs.Close
End Sub

The call that causes the error is :

Call modSecurity.logchg("N/A", "N/A", "LOGON")

Can anyone explain why I get the error ?

TIA
Steve

Nov 13 '05 #13

P: n/a
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\dao360.dll

C:\Windows\System32\stdole2.tlb

C:\Program Files\Microsoft Office\Office10\mscal.ocx

C:\Windows\System32\Inetsrv\cnfgprts.ocx

C:\Windows\System32\mscomm32.ocx

C:\Windows\System32\smsmsg.ocx - This is an ocx I use to send and receive
SMS's

Steve

"Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
Your behavior exactly matches the circumstances I mention below. SO, if you would like to solve the problem:

1) ASSUME YOU ARE WRONG.

2) List your exact references in your response to this message -- including 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 solve the problem. If, on the other hand, you want to keep spinning your wheels and
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" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:c9**********@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 the

table
i.e opening the table and typing in a record,
the first time I get the error, the second time the record is inserted. I
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]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
And if you take out the function calls? You might want to humor me and try it, just for giggles....

Out of curiousity, what are the references?

There is an interesting case where even if all the references are okay

that
a changed path of one of the references typelibs (DLL, OCX, or TLB) can cause a partial reference break because the reference fixup does not

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" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:c9**********@ctb-nnrp2.saix.net...
> I think you are correct, but the problem is I have checked out my
References
> and everything seems to be in order.
>
> Steve
>
> "Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com> wrote in > message news:40********@news.microsoft.com...
> > If I had to guess I would guess that it is complaining about one

of 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.
> >
> >
> >
>
>



Nov 13 '05 #14

P: n/a
Ok, my guess is that at least one (and maybe several) of these libraries are
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 need
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" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:ca**********@ctb-nnrp2.saix.net...
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\dao360.dll

C:\Windows\System32\stdole2.tlb

C:\Program Files\Microsoft Office\Office10\mscal.ocx

C:\Windows\System32\Inetsrv\cnfgprts.ocx

C:\Windows\System32\mscomm32.ocx

C:\Windows\System32\smsmsg.ocx - This is an ocx I use to send and receive
SMS's

Steve

"Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
Your behavior exactly matches the circumstances I mention below. SO, if you
would like to solve the problem:

1) ASSUME YOU ARE WRONG.

2) List your exact references in your response to this message --

including
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 solve

the
problem. If, on the other hand, you want to keep spinning your wheels and
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" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:c9**********@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 the

table
i.e opening the table and typing in a record,
the first time I get the error, the second time the record is inserted. I 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]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
> And if you take out the function calls? You might want to humor me
and
try
> it, just for giggles....
>
> Out of curiousity, what are the references?
>
> There is an interesting case where even if all the references are
okay that
> a changed path of one of the references typelibs (DLL, OCX, or TLB)

can > cause a partial reference break because the reference fixup does not
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" <st****@ufrmsa1.uniforum.org.za> wrote in message
> news:c9**********@ctb-nnrp2.saix.net...
> > I think you are correct, but the problem is I have checked out my
> References
> > and everything seems to be in order.
> >
> > Steve
> >
> > "Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com>
wrote in > > message news:40********@news.microsoft.com...
> > > If I had to guess I would guess that it is complaining about one of 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.
> > >
> > >
> > >
> >
> >
>
>



Nov 13 '05 #15

P: n/a
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\MSInfo32.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 "Installation". 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]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
Ok, my guess is that at least one (and maybe several) of these libraries are 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 need 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" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:ca**********@ctb-nnrp2.saix.net...
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\dao360.dll

C:\Windows\System32\stdole2.tlb

C:\Program Files\Microsoft Office\Office10\mscal.ocx

C:\Windows\System32\Inetsrv\cnfgprts.ocx

C:\Windows\System32\mscomm32.ocx

C:\Windows\System32\smsmsg.ocx - This is an ocx I use to send and receive
SMS's

Steve

"Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
Your behavior exactly matches the circumstances I mention below. SO, if
you
would like to solve the problem:

1) ASSUME YOU ARE WRONG.

2) List your exact references in your response to this message --

including
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
solve the
problem. If, on the other hand, you want to keep spinning your wheels and 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" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:c9**********@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
the table
> i.e opening the table and typing in a record,
> the first time I get the error, the second time the record is

inserted.
I
> 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]" <mi*****@online.microsoft.com> wrote in > message news:40********@news.microsoft.com...
> > And if you take out the function calls? You might want to humor me

and try
> > it, just for giggles....
> >
> > Out of curiousity, what are the references?
> >
> > There is an interesting case where even if all the references are okay > that
> > a changed path of one of the references typelibs (DLL, OCX, or TLB) can
> > cause a partial reference break because the reference fixup does
not > 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" <st****@ufrmsa1.uniforum.org.za> wrote in message
> > news:c9**********@ctb-nnrp2.saix.net...
> > > I think you are correct, but the problem is I have checked out my > > References
> > > and everything seems to be in order.
> > >
> > > Steve
> > >
> > > "Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com>

wrote
in
> > > message news:40********@news.microsoft.com...
> > > > If I had to guess I would guess that it is complaining about

one of
> 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.
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Nov 13 '05 #16

P: n/a
Not sure what is happening here, but note that if all of the files are
installed and registered in locations identical to those on the dev machine
then the bug I describe would not happen (I assume this is why the
"reinstall every freaking thing" steps make stuff work).
--
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" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:ca**********@ctb-nnrp2.saix.net...
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\MSInfo32.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 "Installation". 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]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
Ok, my guess is that at least one (and maybe several) of these libraries are
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

need
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" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:ca**********@ctb-nnrp2.saix.net...
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\dao360.dll

C:\Windows\System32\stdole2.tlb

C:\Program Files\Microsoft Office\Office10\mscal.ocx

C:\Windows\System32\Inetsrv\cnfgprts.ocx

C:\Windows\System32\mscomm32.ocx

C:\Windows\System32\smsmsg.ocx - This is an ocx I use to send and receive SMS's

Steve

"Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
> Your behavior exactly matches the circumstances I mention below. SO, if you
> would like to solve the problem:
>
> 1) ASSUME YOU ARE WRONG.
>
> 2) List your exact references in your response to this message --
including
> 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 solve the
> problem. If, on the other hand, you want to keep spinning your wheels and
> 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" <st****@ufrmsa1.uniforum.org.za> wrote in message
> news:c9**********@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 the > table
> > i.e opening the table and typing in a record,
> > the first time I get the error, the second time the record is

inserted.
I
> > 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]" <mi*****@online.microsoft.com> wrote in > > message news:40********@news.microsoft.com...
> > > And if you take out the function calls? You might want to humor
me
and
> try
> > > it, just for giggles....
> > >
> > > Out of curiousity, what are the references?
> > >
> > > There is an interesting case where even if all the references
are okay
> > that
> > > a changed path of one of the references typelibs (DLL, OCX, or

TLB) can
> > > cause a partial reference break because the reference fixup does not > > 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" <st****@ufrmsa1.uniforum.org.za> wrote in message
> > > news:c9**********@ctb-nnrp2.saix.net...
> > > > I think you are correct, but the problem is I have checked out

my > > > References
> > > > and everything seems to be in order.
> > > >
> > > > Steve
> > > >
> > > > "Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com>

wrote
in
> > > > message news:40********@news.microsoft.com...
> > > > > If I had to guess I would guess that it is complaining about one of
> > 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.
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Nov 13 '05 #17

P: n/a
I've now done exactly what you told me to do -

1) Assumed I Was Wrong
2) Listed References
3) Checked Reference Locations

And I still get the problem.

I accidentally managed to fix the problem (see previous post). Any Ideas ?

Steve
"Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
Ok, my guess is that at least one (and maybe several) of these libraries are 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 need 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" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:ca**********@ctb-nnrp2.saix.net...
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\dao360.dll

C:\Windows\System32\stdole2.tlb

C:\Program Files\Microsoft Office\Office10\mscal.ocx

C:\Windows\System32\Inetsrv\cnfgprts.ocx

C:\Windows\System32\mscomm32.ocx

C:\Windows\System32\smsmsg.ocx - This is an ocx I use to send and receive
SMS's

Steve

"Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
Your behavior exactly matches the circumstances I mention below. SO, if
you
would like to solve the problem:

1) ASSUME YOU ARE WRONG.

2) List your exact references in your response to this message --

including
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
solve the
problem. If, on the other hand, you want to keep spinning your wheels and 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" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:c9**********@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
the table
> i.e opening the table and typing in a record,
> the first time I get the error, the second time the record is

inserted.
I
> 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]" <mi*****@online.microsoft.com> wrote in > message news:40********@news.microsoft.com...
> > And if you take out the function calls? You might want to humor me

and try
> > it, just for giggles....
> >
> > Out of curiousity, what are the references?
> >
> > There is an interesting case where even if all the references are okay > that
> > a changed path of one of the references typelibs (DLL, OCX, or TLB) can
> > cause a partial reference break because the reference fixup does
not > 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" <st****@ufrmsa1.uniforum.org.za> wrote in message
> > news:c9**********@ctb-nnrp2.saix.net...
> > > I think you are correct, but the problem is I have checked out my > > References
> > > and everything seems to be in order.
> > >
> > > Steve
> > >
> > > "Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com>

wrote
in
> > > message news:40********@news.microsoft.com...
> > > > If I had to guess I would guess that it is complaining about

one of
> 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.
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Nov 13 '05 #18

P: n/a
You never did mention if you had verified that the exact path (drive letter,
etc.) for all references was identical on the boxes on which things were
failing (and if the registrations were all correct prior to the extreme
reinstall solution).

When you mentioned the extreme reinstall fixed the problem, I think that
this supports the notion that one of the files may not have been registered
properly. Beyond that I made a specific suggestion to avoid the problem and
now I'll suggest explicit steps to bulletporoof apps:

http://trigeminal.com/usenet/usenet026.asp

A little more work, but it can definitely avoid the extreme solution.
--
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" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:ca**********@ctb-nnrp2.saix.net...
I've now done exactly what you told me to do -

1) Assumed I Was Wrong
2) Listed References
3) Checked Reference Locations

And I still get the problem.

I accidentally managed to fix the problem (see previous post). Any Ideas ?

Steve
"Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
Ok, my guess is that at least one (and maybe several) of these libraries are
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

need
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" <st****@ufrmsa1.uniforum.org.za> wrote in message
news:ca**********@ctb-nnrp2.saix.net...
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\dao360.dll

C:\Windows\System32\stdole2.tlb

C:\Program Files\Microsoft Office\Office10\mscal.ocx

C:\Windows\System32\Inetsrv\cnfgprts.ocx

C:\Windows\System32\mscomm32.ocx

C:\Windows\System32\smsmsg.ocx - This is an ocx I use to send and receive SMS's

Steve

"Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com> wrote in
message news:40********@news.microsoft.com...
> Your behavior exactly matches the circumstances I mention below. SO, if you
> would like to solve the problem:
>
> 1) ASSUME YOU ARE WRONG.
>
> 2) List your exact references in your response to this message --
including
> 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 solve the
> problem. If, on the other hand, you want to keep spinning your wheels and
> 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" <st****@ufrmsa1.uniforum.org.za> wrote in message
> news:c9**********@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 the > table
> > i.e opening the table and typing in a record,
> > the first time I get the error, the second time the record is

inserted.
I
> > 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]" <mi*****@online.microsoft.com> wrote in > > message news:40********@news.microsoft.com...
> > > And if you take out the function calls? You might want to humor
me
and
> try
> > > it, just for giggles....
> > >
> > > Out of curiousity, what are the references?
> > >
> > > There is an interesting case where even if all the references
are okay
> > that
> > > a changed path of one of the references typelibs (DLL, OCX, or

TLB) can
> > > cause a partial reference break because the reference fixup does not > > 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" <st****@ufrmsa1.uniforum.org.za> wrote in message
> > > news:c9**********@ctb-nnrp2.saix.net...
> > > > I think you are correct, but the problem is I have checked out

my > > > References
> > > > and everything seems to be in order.
> > > >
> > > > Steve
> > > >
> > > > "Michael (michka) Kaplan [MS]" <mi*****@online.microsoft.com>

wrote
in
> > > > message news:40********@news.microsoft.com...
> > > > > If I had to guess I would guess that it is complaining about one of
> > 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.
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Nov 13 '05 #19

This discussion thread is closed

Replies have been disabled for this discussion.