Newbie input mask Q and paswords setting

[Cincity]

Sorry if this has been asked before, or if it is in the wrong place.
I have a couple of questions/problems........



1). I am trying to set an input mask for !>L0000000;;- where 'L' needs to be either X or Z, and no other letters allowed. I cannot seem to get it sorted and its doing my head-in.

2). I am also trying to restrict a series or part numbers that are allowed into a field in a linked table. The part numbers that can be allowed are dependant on a parent part number. For example, parent part number 12 can only have sub components 3, 5, and 23 in it - all others wont be allowed. In total, I have 60 parent part numbers, and in-excess of 40 sub components. These can be put onto a spreadsheet if necessary.
Not sure if that info helps any.

3). Finally, can I assign passwords to certain 'buttons' in the switchboard window?

Thanks in advance. 1, or 2, or 3, or all would be very much appreciated

[NTC]

3) yes, just a little VBA added to the command button code...not sure how you want to implement it...perhaps an unbound text box next to the command button so the user enters the PW then presses the button...or maybe a popup form...

2) just lots of grunt work code logic to insert. hopefully you are paid by the hour! excel doesn't offer any ease on this.

1) as you are probably aware - there is no mask symbol that inherently limits it to X or Z. maybe something creative - such as offering the user a dropdown of only those 2 letters - and an unbound textbox for the remainder info....and then merge that data together with a bit of VB behind the scenes.

[Cincity]

Thanks for the response
Paid by the hour - Hahaha. Nice thought.

It is my first database, possibly my only one, and is being done as a final project for part of an engineering degree.

I have no experience of coding, macros, or input masks etc etc so getting to the current stage has been .......time consuming, very frustrating, but somewhat satisfying in a sick if twisted sort of way. However, I am beginning to think that these bells and whistles may for ever remain 'not-fixed'.

Point 2 would have been the nicest 'to-have' but the database is working ok without it.

Thanks again