Search results

Put an invisible text box with the value set to 1 in your detail section. Set its property to running sum. From the OnPrint event, check for the value and accordingly force the new page: If Me.Controls("YourControlName") \ 30 = 0 then ForceSectionToNewPage ("NameOfYourReport"...

If the number and relative places of letter and numeric characters are know in advance (ie a format exists) the easiest way is to make an input mask. It will allow you to constraint the number of characters, the type of each character (number, letter, either one or another), if they are...

1. To place the cursor somewhere use : Me.Controls("YourControlName").SetFocus 2. Let the user cancel the new record: From the field beforeupdate event, test for the value entered using something like: If Len(Nz(Me.Controls("YourControlName").Text,""))=0 then If MsgBox (...)=vbCancelthen...

have a look to the ongoing thread: Never store a built ID, just display it. Ex ample of Year-Number ID

For your first question, do a search on 'cascading combo'. You will find many threads treating that subject. Ex: Cascaded combos Regarding the second, use the combo boxes wizard (make sure you have it installed, it may be optional when installing access). One of the proposed choices is to create...

I believe you have split your DB FE (not replicated interface) / BE (replicated data). I do use tables with system values that are on principle constant or at least specific to one given replica. I just let those system values tables in the not replicated FEs... As for synchro over the...

After you've built your strSQLSF add this line of code: Debug.Print strSQLSF to have the value of strSQLSF displayed and checkable in the immediate window after the code is run.

If you are sure that your users wil never do anything else than adding new records, your method should be sufficient and replication an overkill. In any other case (possible updates, deletions, etc.) you will HAVE TO look into replication.

1. You have to make a choice between Pat's suggestion and mine. They are fundamentally the same with one difference: Pat provided you with a formula that simulates an autonumber and WILL RESET for each different year (ex: 02_00001, 02-00002, 02-00003, 03-00001), but you will have to manage...

Did you try Ctrl+Enter

There actually are a few functions for that purpose. Have a look to 'SelStart' in Access Help

And sacrifice a few bugs at noon to Bill Gates, according to ritual procedures only shared among programmers. ;)

BTW, you will notice that your autonumber will continue numbering starting from the highest value you imported in your table. And if that number is already high you will feel relieved to have followed my advice (because your 00-00000 format would have failed as soon as the autonumber reaches...

ksGirl, I am going to tell you what I believe is the best to do and that I would most sincerily do if I were in your case. I had VERY painfull experiences with built-and-stored Primary keys when I worked on replicated DBs and sweared I would never go into this again. I would: 1. Seek to save...

Yes you will have to. Something like Me.Controls("YourControlName").Text = strconv(Me.Controls("YourControlName"), vbProperCase) in the Before Update event of the form.

I know it is demanding much for someone like you, Rich. But try to keep serious an do some useful work, for a change. I don't know... For example, find Title for me! :) BTW, I thought I had some understanding of French, but while I know what is 'bas' and 'bleu', 'bas-bleu' is something new to...

The formula I provided to you can be used to store the result in your underlying table if you really want to. But you should not. Make a new field to store the year instead. Then, at any moment, you can retrieve the serial number by using the formula. If you store the result of the formula, you...

Then, in the controlsource of a control on your form, put: =Format(Now(),"yy") & "-" & left("00000",5-len(cstr([ID]))) & [ID] where ID is the name of a textbox (eventually hidden) of your form, bound to the autonumber ID of your records. but you will run into troubles if your autonumber happens...

At the right of the recordsource property of your combo, you will see these three points. Click on them and the QBE grid will be displayed, gather the fields you want as you would do for a query, then shut the grid. you combo is now based on a query and will display with each column...

ksGirl, It is possible to do what you want, but as Pat suggested you should explore alternatives first, like using an internal autonumber and only displaying your built key on will (not storing it, much less even using it as a primary key) Ex: use an internal autonumber and a textbox to...