I have screen shots of what I have in my db, where can I send it to you (it is in word format) so that you can take a look at it to see what I am doing wrong. I took a screen shot of what is listed for the button and I took a screen shot of the text box Job No. I don’t know how to bound anything other than put the code behind the button and putting the Job_No in the code as you stated. I understand what you are saying, but I thought if I put the text box name Job No in the code behind the button then it would be bound to my table with the Job No field. Heeeelllllppppp!!!! I am sorry that I can’t seem to grasp this….but appreciate all of your help!
Here, you’ll be given the chance to name your AutoText entry. Name it carefully — for AutoText to work correctly, the first four letters of each of your AutoText entry names will need to be distinct, since these first four letters will be the prompt for Word to offer to complete the phrase for you. My suggestion is to use Interrogatories, Production and Admission as your names, but use whatever is convenient and memorable for you.
Remember that you must update the values in the sheet if you want to continue the numbering series with the next batch of tickets. For instance, if you want your next batch of tickets to start with 112, you'd open the workbook and change the value 100 to 112, and update the remaining values accordingly. Don't forget to save the workbook after updating the values.
The expression: Nz(DMax(“[PONum]”,”tblPO”),0)+1 will check if a PONum already exists. If it doesn’t it returns a 1, if it does it returns the number incremented by 1. If the number exists, but is 0 it will return a 1. In my blog I advise that number should NOT be generated until the user is ready to save the record. And to immediately commit the record after generating the number. Therefore, there should be no issue about giving them a new number if they go back to it.
To design a certificate from scratch, you can either start with a completely blank publication or adapt an existing publication. Small-sized publication types, such as business cards, postcards, and labels can be adapted to serve as coupons. Flyers or brochures can be adapted for use as gift certificates. For more information, see Create a publication in Publisher.
Now, what’s the deal with the UniqueKeyVariant parameter for the RowNumber() function? We are not even using it all! True, but if we didn’t, Access will call RowNumber() only once for an entire query and thus we get “1” for the entire dataset. That is a good way to save on CPU processing – why call Now() for each row? In this case, we want to go against this CPU-saving measure and ensure that the RowNumber() is in fact called once per row to generate a new number for that row. Thus, we pass in a parameter — a primary key of a table is a good choice for this purpose. So we get a nice sequential number generated all in the query with VBA function.
So, as an example, I’ll start with the style linked to the interrogatory in my multi-level list, type my question, hit return and I’ve got the answer space. Return again, another interrogatory ready to go. Wanted request for production instead of interrogatory? Hit the tab key and it switches to the next list level, which is request for production. (I hope I’ve explained this well enough.) sequential numbering in publisher