Search results

thats great - thanks for the information there... I will read, in earnest....

.. no I didnt...

OK - so I have created a brand new DB file from and imported all but the offending Switchboard form.... I have then imported the Switchboard file from my backup (that I know does work without issue..).. and all appears well! Thank you. ....the overriding question remains why I have to go...

.. I havent... I will now... but what do I do about the Switchboard.. this is quite literally the front end of the application...

Respectfully, that is exactly what I have described at the top of this thread... it wont import the new Switchboard file....

I cant even find any way of showing the System Tables (as you used to be able to in earlier versions of Access), with a view to modifying to remove references to the old Switchboard form - which may be the reason for the import failure....

Hi again... ! I have deleted the Switchboard.... If I try and import from another copy of the DB... the import fails.. without any message....

.. no it isnt...

(I have this periodic/recurring issues from time to time when making changes to the database file... ) Access Version : Office 365 This morning went into design mode to view a Switchboard forms VBA code... then closed it without making changes... I then ran the Switchboard panel (the primary...

Thanks, but i don't have this issue as the records on this dialog are created elsewhere ..

Hey Bro, that worked a treat.. thank you very much.

.. thats much the same as what I have, the issue is that the visible status is set for ALL instance of the fourth checkbox... (see the pic)

No - only text boxes/labels...

I have a continous form as shown attached. I have three checkboxes that display on each row - and a fourth checkbox on the right hand side that must ONLY display when the other three on the left have been checked. To do this, I have a sub() call in AfterUpdate() on each of the 'three'...

Respectfully, I have paid attention to detail but perhaps have been blinded by staring at the code for so long and running various different scenarios that were complicated by shortcut menus created by Macros that were also assigned to the form ... (long story) However, with all the errors I...

OK - so I foind on StackOverflow some helpful tidbits... and in a nutshell... 1. You need to declare the subroutine as Public AND in a Public Module (it cant be declared local to the form you are working in ...) 2. In order to use a parameter, use the .Parameter attribute of the command button...

>>Your original approach (.OnAction = "=PlanningSheet()") should work for functions, while @MarkK 's >>approach should work as well, but for sub procedures. No - it doesnt... try a simple commandbar demo using a call to MsgBox against the .OnAction attribute... it does nothing...

So Im not making any progress on this at all.. I can create the commandbar and a button and this initially displays as a shortcut menu. When I attempt to do it again in the same session.. when it checks that the commandbar doesnt exist.. if it exists, it attempts to delete it... I get the...

Regretably, this doesnt work. With a breakpoint on the mnuPlanningSheet function - no interrupt / ie. it doesnt call it... Tried declaring a function local to the form that is called from this menu option - no parameters, simply to display a msgbox .. same result, function is not called...

So I have the context menu displaying correctly and I am using .OnAction to qualify the VB function to run when the selection from the menu is made..., but it is not running the routine in each instance...? Set newbutton = myBar.Controls.Add(msoControlButton, 1, Me.txtJobNumber)...