1) I have placed all the screens to the left and towards the top so that the client (myself and a couple of folks) can use it on the computer at work that is set at 800x600. I hope that this will not bother you when trying to help.
that's fine, however, you did not say there were only three buddies using this with idential screens and resolutions. i merely wanted to point out what seemed to me as a design error - i was not to know that you were not going to be passing this DB on who may have a different screen to the one you have specifically made your DB for.
2) The colors I have chosen are working fine on my home computers and the ones at work including a lap top. They are open for changes but they are not the problem that I have asked to be looked at.
i apologise for bringing to your attention the fact that other people may not physically be able to see the data in your database. if you and your buddies are happy with that, then fine. i just wanted you to develop a database for a wider audience whom you may not know. since you have pointed out that you are only a small group of people and everyone's happy, i suppose that's not an issue. you didn't say it in the first instance, so how was i to know.
3) If you follow the directions that I have given, you will see that if you type in the 000 111 it will add it to the database and you can track it on future days. By the way, it will beep to let you know that it is not in the database so you don't have to guess if it is or not. When you type in the 002 RBR the full license will display with only a few key strokes...when you tab all the rrecords come up for it....this saves a lot of keystrokes.
well, i usually have my computer set to mute, so as not to annoy the other commuters on the train and colleagues in the lab office. the fact that it beeps tell me nothing. and the message box isn't helpful. again, if there are only three of you and you all know what the deal is, then fine, but if you were to distribute this DB to a wider audience, a lot of people would become confused.
4) Since only 3 of us will be using the database and all three of us are prior or active military, I went with military dates without the spaces to save on keystrokes. Hence the 28feb09 will give the correct date. The field is a date field with an input mask of the military date without the spaces.
ok, again that's fine, since all of you to be using the DB are happy about it. and how in heck was i supposed to know any of that was military? i've never been in the military, of any country, so any of your 'violations' terms and things are completely foreign to me.
5) The time is the same as the date. It is a time field with military time without the colon to save keystrokes.
that's just the issue: i DID put it all in 'military' (i.e., 24-hour time, for everyone else) style and without the colon - and it still gave me that error.
even though you DID NOT ASK FOR HELP on THIS issue, i thought,
in good faith, that i ought to point it out to you.
6) If the CTRL + TAB isn't convient then what would you suggest to get back to the search field? I figured that this is a conventional key stroke for access and was alright to follow.
my suggestion is [edited word order] to not hide [/edit] the search field at all. not sure what you mean by 'convetional key stroke for access'...?
7) I can see that it would take a long time to enter the almost 6000 records using the mouse. I am trying to set this database up using teh fewest keystrokes and no mouse movememts as it wastes time.
first, your instructions said EXPLICITLY to use the TAB key. this implies that it will not work any other way. your instructions to US was to enter just ONE record - i have no dispute that to enter 6000+ records tabbing will be a good solution, but again, you did not specify this. you COULD have said "enter this data - for conventience, you can use the tab key if you're entering 6000+ records to make it faster" rather than "..then press tab, then enter blah, then press tab, then enter blah, then press tab..."
people know that, generally, tab is a way to move through the fields of a form. if you say EXPLICITLY to use the tab key, then it can be assumed that you hav ecoded the DB specifically only to accept the data if only the TAB key is pressed. this was not the case, so i thought i should point it out to you IN GOOD FAITH... sir.
8) That is right as it is a new license in the database as the message box indicates along with the beep.
the message does NOT indicate that this it is creating a new record/license. what it specifically says is that this license is not already in the database - that's two VERY different scenarios. you have to understand at this point that many people code their DB TO NOT ALLOW further entries, so this message box could easily confuse (however, again, if your group of intimate three are happy with this, that's FINE)
9) I guess you need to look at some license plates. a 002RBR is not the same as 002 RBR....they are two different plates and will be treated as that. Some licenses are 888 9999, ABC 123, HW 89 HY65....you have to be able to input almost everything so there is no formatting that can be done.
i looked at ALL your license plates before i started. they ALL had the format XXX[space]XXX - which is the ONLY reason i mentioned it. i would NOT have said anything if there were even the small number of variations that you have just now decided to inform us of.
again, you may not have asked for this, but i just wanted to point this out to you for making everything easier - besides, i thought you wanted military execution WIHTOUT superfluous keystrokes??? in which case leaveing off the spaces at data entry would still be a valid option - the only question would be whether there is the possibliity that license "000 111" could exists as well as "000111" - surely whoever it is that creates these licenses must be aware that those two licenses are extremely close in nature?
10) You guessed it....I don't have any CTRL + TAB business cause it is a standard keystroke for access.....I will try to post the code in my next message.
i don't know about this keystroke or what it does or how it functions. and i do apologise for not being able to help you on this point.
i would urge you to revisit these point if ever you decide that your DB needs to be distributed to a wider audience. at the moment, if it's working for you, then ok. but please don't be surprise if one day someone comes to you asking again how to use this or that or saying there are bugs in it...