Search results

Like Rich said if you want print data the best way to do it is with a report. If you need to print the form for layout and development purposes try doing a screen grab and then printing it from paint. If you still want to print the form try setting the form to layout for print. On individual...

What? Since when did I get up at 0630 on a Sunday? More like 1330 :D I never heard Mike get angry why do you mention him? I am much more mardier than him. ;)

Come on these wizards are not that great. How fast can you type? I am all for automation but these wizards hardly do anything to help me save time they are just the very basic functions and are poor on layout. You are better off creating your own automation if you want to save time.

It's not a question of 'decided' it's a question of good design. Lots of tightly packed fields, and narrow pages makes it difficult to read and often completely unnecessary. If you are going to use it like this than you might as well just use a table as the child. Idiot proofing is a large part...

I think that's about right maybe I was overreacting a little bit. I don't really use wizards very often only occasionally for controls. Obviously it is not the wizards themselves that are problem more a lazy haphazard approach to design and being too reliant on wizards and lack understanding of...

Yes there are times when continuous forms are appropriate true but the majority of times they are used inappropriately. Most of the time they look extremely messy and difficult to read especially if a wizard has been involved. I said that subforms should be used sparingly what you talk about is...

The idea of a data entry interface is you enter a single new record. The idea of a data view/edit interface is to view the records and edit them. Of course you can still add new records when you are in data view but I think it is important to make a distinction between data entry and data...

Is it just me or are lots of people are relying too much on wizards and not considering the best design for the user interface? Access has great capability for interface design. I blame those bloody 'made simple' guides for not emphasising the importance of good design. Also many don't...

Set Data Entry to No on the form's properties.

Sorry I thought I was answering the original person. Now I'm confused. :confused: :o

You are saying the form is continious then possibly the 'field' is the same field just the second record. When you say field are you talking about a textbox, etc? To move to the second record use: DoCmd.GoToRecord , , acGoTo, 2 If I'm wrong about that: What is the name of the second field...

Did you use api and if so which functions?

Warren when you used the wizard it asked you what table you wanted to reference from i.e. to be the dropdown list of the combo box and the table you wanted the result to be entered into. RowSource is a property of the combobox and you can set manually by right clicking on it and selecting...

As long as you cap the total string length it doesn't matter if it changes. You have to have a good reason for doing that way though. Can't deny that I have done it this way to save code.

Cont.SetFocus Cont.SelLength = 0 Where Cont is the name of the second field.

Or you could type it in as text if you only have a few options and it is not going to change much.

Have you bound the combo to the table you want to enter in? What does it say under the form's properties for allow edits and allow additions?

Quite simple use the Listindex property of listbox to select the item you want. You need to put the Listindex into an integer or long dim and after you resort the list set the Listindex by the ListIndexDim +/- 1. The listbox has to be in focus before you use this property.

When you have KeyPreview activated on a form you can trap these in the KeyDown, KeyPress and KeyUp events. By setting KeyCode = 0 you are cancelling what ever the key is supposed to do. By placing what you want it to do after cancelling what it wants to do prevents a mess of both. Get it. As...

Holey moley :eek: I'm not even going to ask. Try cancelling the key before the DoCmd.GoToRecord it makes more sense. I also changed Enter to save the record rather than just go next. Like: Private Sub Form_KeyDown(KeyCode As Integer, Shift As Integer) On Error GoTo Err_Form_KeyDown Select...