PC Review


Reply
Thread Tools Rate Thread

Was working...now producing error...

 
 
=?Utf-8?B?YWxieWNpbmR5?=
Guest
Posts: n/a
 
      10th Nov 2005
The following line of code was working fine before I went on holidays, now
I'm back and whenever I open the form it tells me there is a problem with
this code......why?

"The expression On Current you entered as the event property setting
produced the following error: Procedure declaration does not match
description of event or procedure having the same name." WTF?

Me.cmdCarrier.Enabled = Nz(Me.CarrierClaim.Value, False)

cheers
 
Reply With Quote
 
 
 
 
Douglas J Steele
Guest
Posts: n/a
 
      10th Nov 2005
The error message is saying there's something wrong with whatever you've got
as the procedure to run on the form's Current event.

Open the form's properties, and find the On Current property on the Event
tab. What's beside it?

If it's the line of code you have posted, you can't put that as a event
procedure: it must be either the name of a macro in your database, the name
of a function in your database (preceded with an equal sign), or the text
[Event Procedure] (complete with square brackets).

If it's [Event Procedure], click on the ellipsis to the right (...), and
make sure that the procedure to which the VB Editor opens starts Private Sub
Form_Current( ). If there's anything in the parentheses, that's the problem.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"albycindy" <(E-Mail Removed)> wrote in message
news:9C04F562-D4A0-44DF-8454-(E-Mail Removed)...
> The following line of code was working fine before I went on holidays, now
> I'm back and whenever I open the form it tells me there is a problem with
> this code......why?
>
> "The expression On Current you entered as the event property setting
> produced the following error: Procedure declaration does not match
> description of event or procedure having the same name." WTF?
>
> Me.cmdCarrier.Enabled = Nz(Me.CarrierClaim.Value, False)
>
> cheers



 
Reply With Quote
 
 
 
 
=?Utf-8?B?S2Vycnk=?=
Guest
Posts: n/a
 
      10th Nov 2005
It might be (and only might be) a broken or bad reference to a library. Go to
Visual Basic, click Tools, then References and make sure you have the
Microsoft Access X.X Ojbect Library (X.X is probably 11.0 for 2003). Nz() is
a function of this library.

"albycindy" wrote:

> The following line of code was working fine before I went on holidays, now
> I'm back and whenever I open the form it tells me there is a problem with
> this code......why?
>
> "The expression On Current you entered as the event property setting
> produced the following error: Procedure declaration does not match
> description of event or procedure having the same name." WTF?
>
> Me.cmdCarrier.Enabled = Nz(Me.CarrierClaim.Value, False)
>
> cheers

 
Reply With Quote
 
=?Utf-8?B?YWxieWNpbmR5?=
Guest
Posts: n/a
 
      10th Nov 2005
There's nothing in the parentheses...

Private Sub Form_Current()
Me.cmdCarrier.Enabled = Nz(Me.CarrierClaim.Value, False)
End Sub

There is [Event Procedure] etc etc I know all that stuff, I just don't see
why something should work two weeks ago and not now (nothing changed).

"Douglas J Steele" wrote:

> The error message is saying there's something wrong with whatever you've got
> as the procedure to run on the form's Current event.
>
> Open the form's properties, and find the On Current property on the Event
> tab. What's beside it?
>
> If it's the line of code you have posted, you can't put that as a event
> procedure: it must be either the name of a macro in your database, the name
> of a function in your database (preceded with an equal sign), or the text
> [Event Procedure] (complete with square brackets).
>
> If it's [Event Procedure], click on the ellipsis to the right (...), and
> make sure that the procedure to which the VB Editor opens starts Private Sub
> Form_Current( ). If there's anything in the parentheses, that's the problem.
>
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
>
> "albycindy" <(E-Mail Removed)> wrote in message
> news:9C04F562-D4A0-44DF-8454-(E-Mail Removed)...
> > The following line of code was working fine before I went on holidays, now
> > I'm back and whenever I open the form it tells me there is a problem with
> > this code......why?
> >
> > "The expression On Current you entered as the event property setting
> > produced the following error: Procedure declaration does not match
> > description of event or procedure having the same name." WTF?
> >
> > Me.cmdCarrier.Enabled = Nz(Me.CarrierClaim.Value, False)
> >
> > cheers

>
>
>

 
Reply With Quote
 
=?Utf-8?B?YWxieWNpbmR5?=
Guest
Posts: n/a
 
      10th Nov 2005
Checked that too. (Object Library 9.0, only access2000....)

Anyhoo....! Somehow it seems to be working now...which is strange, because I
have changed nothing!! Have only been familiarising myself with what I last
did a few weeks back...this computer is weird!!!

"Kerry" wrote:

> It might be (and only might be) a broken or bad reference to a library. Go to
> Visual Basic, click Tools, then References and make sure you have the
> Microsoft Access X.X Ojbect Library (X.X is probably 11.0 for 2003). Nz() is
> a function of this library.
>
> "albycindy" wrote:
>
> > The following line of code was working fine before I went on holidays, now
> > I'm back and whenever I open the form it tells me there is a problem with
> > this code......why?
> >
> > "The expression On Current you entered as the event property setting
> > produced the following error: Procedure declaration does not match
> > description of event or procedure having the same name." WTF?
> >
> > Me.cmdCarrier.Enabled = Nz(Me.CarrierClaim.Value, False)
> >
> > cheers

 
Reply With Quote
 
=?Utf-8?B?S2Vycnk=?=
Guest
Posts: n/a
 
      10th Nov 2005
Gosh, sounds like normal Access! :-))

Glad it's now working, but I know it's frustrating 'cause you don't know
when it'll do it next.

Kerry


"albycindy" wrote:

> Checked that too. (Object Library 9.0, only access2000....)
>
> Anyhoo....! Somehow it seems to be working now...which is strange, because I
> have changed nothing!! Have only been familiarising myself with what I last
> did a few weeks back...this computer is weird!!!
>
> "Kerry" wrote:
>
> > It might be (and only might be) a broken or bad reference to a library. Go to
> > Visual Basic, click Tools, then References and make sure you have the
> > Microsoft Access X.X Ojbect Library (X.X is probably 11.0 for 2003). Nz() is
> > a function of this library.
> >
> > "albycindy" wrote:
> >
> > > The following line of code was working fine before I went on holidays, now
> > > I'm back and whenever I open the form it tells me there is a problem with
> > > this code......why?
> > >
> > > "The expression On Current you entered as the event property setting
> > > produced the following error: Procedure declaration does not match
> > > description of event or procedure having the same name." WTF?
> > >
> > > Me.cmdCarrier.Enabled = Nz(Me.CarrierClaim.Value, False)
> > >
> > > cheers

 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
keyboard producing wrong characters in XP Badger Windows XP Help 0 3rd May 2005 07:22 AM
keyboard producing wrong characters in XP Badger Windows XP Help 0 3rd May 2005 07:21 AM
keyboard producing wrong characters in XP Badger Windows XP Help 0 3rd May 2005 07:18 AM
keyboard producing wrong characters in XP Badger Windows XP Help 3 3rd May 2005 02:32 AM
Keyboard keys not producing the correct symbol =?Utf-8?B?Rm9yZXN0X3JlZA==?= Windows XP Help 1 31st Oct 2004 12:39 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 04:55 AM.