dbTalk Databases Forums  

Problem with switchboards & forms

comp.database.ms-access comp.database.ms-access


Discuss Problem with switchboards & forms in the comp.database.ms-access forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Chris Bolus
 
Posts: n/a

Default Problem with switchboards & forms - 11-07-2003 , 05:31 AM






I'm a teacher using MS Access on an RMConnect 2.4 network. On some
workstations both I and my students sometimes get an error message
when attempting to use a command button on a form which reads "Invalid
use of null". The remainder of the options are then unavailable and
the button wil not work.
The only solution is to log on to a different workstation.
Any ideas?

My second problem is more user-specific, and has so far only affected
two students. Again this is associated with command buttons, either in
forms or switchboards, such that when the button is clicked an error
message comes up to the effect of "Ambiguous name
detected:books_click" (actual name varies). This usually loads the
Visual Basic debugger, which is outside the scope of what my students
are doing. I don't have enogh knowledge of Vbasic to sort this anyway.
Again, any ideas?

Reply With Quote
  #2  
Old   
John
 
Posts: n/a

Default Re: Problem with switchboards & forms - 11-07-2003 , 08:00 AM






hi Chris,

Im just guessing here because I dont know what your forms/buttons do,
but invalid use of null is usually associated with data being passed
around in vba. If you have variable data being processed then perhaps
something is coming up NULL which should contain a value. It gerally
requires debugging.

The other problem is simpler, or should be, but still requires working
in the vba module. An ambigous name for a procedure call (books_click
in the case you mentioned) means that there is more then 1 procedure
in the vba module by the same name. This usually happens when a coder
decides to rewrite a click event and forgets to delete the orphaned
event procedure, leaving 2 procedures of the same name. I suppose it
could also happen if a procedure that creates procedures on the fly is
run more then once with poor error checking. Im not if this is a
problem associated with the switchboard or not since i dont use
switchboards. It's a religous thing I guess <g>

regards,

John
jobrien at acscience dot com


google (AT) b0lus (DOT) com (Chris Bolus) wrote in message news:<8dbd488.0311070331.231db0b0 (AT) posting (DOT) google.com>...
Quote:
I'm a teacher using MS Access on an RMConnect 2.4 network. On some
workstations both I and my students sometimes get an error message
when attempting to use a command button on a form which reads "Invalid
use of null". The remainder of the options are then unavailable and
the button wil not work.
The only solution is to log on to a different workstation.
Any ideas?

My second problem is more user-specific, and has so far only affected
two students. Again this is associated with command buttons, either in
forms or switchboards, such that when the button is clicked an error
message comes up to the effect of "Ambiguous name
detected:books_click" (actual name varies). This usually loads the
Visual Basic debugger, which is outside the scope of what my students
are doing. I don't have enogh knowledge of Vbasic to sort this anyway.
Again, any ideas?

Reply With Quote
  #3  
Old   
Chris Bolus
 
Posts: n/a

Default Re: Problem with switchboards & forms - 11-09-2003 , 11:15 AM



jobrienct (AT) excite (DOT) com (John) wrote in message news:<c4916e0f.0311070600.603cef1e (AT) posting (DOT) google.com>...
Quote:
hi Chris,

Im just guessing here because I dont know what your forms/buttons do,
but invalid use of null is usually associated with data being passed
around in vba. If you have variable data being processed then perhaps
something is coming up NULL which should contain a value. It gerally
requires debugging.
This happens before a button is even created; during the command
button wizard. It makes it impossible to finish creating the button.

Quote:
The other problem is simpler, or should be, but still requires working
in the vba module. An ambigous name for a procedure call (books_click
in the case you mentioned) means that there is more then 1 procedure
in the vba module by the same name. This usually happens when a coder
decides to rewrite a click event and forgets to delete the orphaned
event procedure, leaving 2 procedures of the same name. I suppose it
could also happen if a procedure that creates procedures on the fly is
run more then once with poor error checking. Im not if this is a
problem associated with the switchboard or not since i dont use
switchboards. It's a religous thing I guess <g
Well the reasoning behind using switchboards in GCSE coursework is
that it makes it easier to write a User Guide for their system. These
are students whose computing knowledge is not strong ib the first
place, so of course using Access is difficult for them anyway.


Reply With Quote
Reply




Thread Tools
Display Modes

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

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.