User Defined Combobox Defaults on Bound Combobox?

[unluckytoe]

Hello All:

I have a question...I need to have the option of the users who are using their own front ends to be able to select their own defaults in several bound comboboxes on a single form. These defaults constantly change during the day, so programming the default value will not work for this instance.

Any help would be awesome! If I need to supply anyone with more information, just let me know.

Brian

 

[Galaxiom]

Make a table to record the defaults for each user and use these records to set the value of the control when the form is opened. A DLookUp of the table as the Default property of the control is an easy way to retreive it.

A form based on this a query of this table can be used to set the defaults. Another way is to use a button to run an Update command to save the current values held in the controls.

I prefer a central table so users get their defaults wherever they connect from. Other developers might choose to store the users settings in a local table in their version of the front end.

However I firmly believe any front end should be entirely static and the use of local tables inside a front end is a very common bad practice. A static front end never requires compacting and cannot be corrupted. Local tables should be in what I call a "Side End".

 

[unluckytoe]

Galaxiomathome:

This sorta makes sense to me, I'm still very new to Access 2007, is there a demo of this that I can download from somewhere? It's easier for me to learn if I see it, if not, how would I start?

Thanks for your help:

Brian

 

[unluckytoe]

Hey All:

After a lot of searching and trial and error, I have this code:

Private Sub Check782_AfterUpdate()
If Me.Check782 = True Then
Me.Tracking_Number.DefaultValue = """" & Me.Tracking_Number.Value & """"
Else
Me.Tracking_Number.DefaultValue = False
End If
End Sub

It saves the last input and carries it over to the next record, which is perfect, but I don't want to have all of the users to have to close the form to reset the valves. Another problem is that when you untick the checkbox, a "0" (without quotes) shows on the next record. I like this method of being able to select via checkbox which control (either text or combo) so if anyone could help that would be fantastic.

Thank you again:

Brian

 

[unluckytoe]

just a friendly bump, seeing if anyone out there could help me out.

Thanks,

Brian

 

[jdraw]

just a friendly bump, seeing if anyone out there could help me out.

Thanks,

Brian

Did you try GlaxiomatHome's approach?
You'll need a list of Users and for each user the default value you'll assign.
You might wish to elaborate on exactly what you are doing to help put all of this into context.

 

[unluckytoe]

jdraw:

No I couldn't figure out his method.

What we do here is prep hundreds of cell phones and laptops for our customers. When we are ready for deployment, we bar code scan all data into access. However, to reduce the amount of actual clicks, we would like to use defaults to control the specific fields (i.e sometimes the shipping address is the same for 100 devices)

This isn't the case with all the controls though. Sometimes we have one offs, and others we have up to 10,000 devices being deployed. In many cases we don't always record the same data, air cards vs. netbooks have different data that needs to be recorded, and in some cases all the controls at any given time would/could need to have defaults set.

Having some defaults will reduce the amount of time for our users. I hope this makes sense, I haven't had my coffee yet!

Thank you for your time:

Brian

 

[Galaxiom]

Part of this appears to be more of a normalization issue than about defaulting values. For example you do not need to repeat the same shipping address information 100 times.

As a simplistic example, in the case of the shipping address, separate this into a different table. Use the primary key for these records as a foreign key in the Items table.

Use the shipping address table as the record source for a main form.
Use the Item table as the record source for a subform. Set the Master and Child Link Fields as these key fields.

The user then selects the required record for the shipping information. As the subform records are entered they are automatically populated with the foreign key matching the current main form record.

This approach can be generalised to other common data but without knowing more about the range of information being recorded it is difficult to be specific.