Search results

Go into design view, click on the text box for the date and click and drag on the edge of the box to make it longer.

See attachment, I made changes to your sample two stuff- check out the sample 2 table, query and the form I made.

btw.... Both of your samples are wrong....

Yep that is exactly right. I have hear that it is OK, during the design phase to have them because it is easier to set up forms and such, but then you should go back later and remove the lookup from the field in your tables, but the combo boxes and such will remain. I am not quite sure why...

Are you sure you're not using a text field, it's maximum is 255, but a memo field can hold way more. Edit: Oops, Bob beat me to it....

See here for the evils of lookup fields.

I have come accross that too! It is so annoying!

Did you get this figured out?

Bob, please correct me if I'm wrong, but I don't think unbound or bound effects what events are viable or not. the before update and after update events would still fire, so you can still use code, I just tested before update, and it worked.

To do a check for the value, use either the before update, or after update events I would think.

Aha, I see.... I think somewhere deep down inside of me that I really did know that. :o

After normalization, wouldn't using a continuous subform with no border on the control be an easier way, you wouldn't have to code anything? Just set the subform to "can grow" or "can shrink", And use the check box on the main form to filter the subform, one record or all records, or something...

Check this out and see if it helps

Would it be a good idea to have it convert to oz on record after update, so that everything is stored as oz, and can be converted as needed? Or because of the application to have it done your way?

Oh, just read the rest. You could have a form that has two text boxes (unbound), one for lbs and one for oz.... on the record update you could have it convert the lbs to oz and add it to the other text box and then store the total oz in your table record or something like that.

How about having a weight field, then a unit of measure field, the unit of measure field could store a fkreference to a pkreference in a unit of measure table that stores, lbs, grams, oz, etc... Then in your form, you could have a combo box that pulls from that UOM table, and when the weight is...

Happy Birthday! :D

Wow, crazy, I am glad your house wasn't hit.

Welcome to AWF PabloBB

Oblivion is the best game ever!!!! Of course I only ever had it on the 360...