Search results

I use code that does it from a combobox. I just assign the combo selection columns to the appropriate textboxes in the form. Me.YourTextBoxName1 = Me.YourComboName.Column(1) Me.YourTextboxName2 = Me.YourComboName.Column(2) Me.YourTextBoxName3 = Me.YourComboName.Column(3) And So forth ...

That is exactly what happens. It doesn't matter how you order the query externally, the internal ordering in the report takes precedence. Of course, I had to learn this truism the hard way - which resulted in me banging my head against the wall for a few days. :)

Maybe that's why you're here ... I'm here for the great pay and benefits ;)

Take out all personal information, remove data from tables (just leave enough for it to work) then do a compact and repair. (TOOLS/ DATABASE UTILITIES/COMPACT and REPAIR DATABASE) Once you have done that, zip the db. It must be less than 393KB when zipped. If it is still too large, remove some...

That's excellent news. I was playing around with it at work today and had come to the conclusion that it had to have something to do with how the query was populating the combo - since all other possibilities had been looked at. But as usual, Bob to the rescue. :)

I had the same problem with the db. However, I have no problem with Paul's example.

I agree. I did a quick login form for another program that I have and used the Public variable pCurrentUser to assign the login name on the Oncurrent event for another form (me.text86=pCurrentUser) - and no problems. So I think it's probably something simple.

Please do. There's probably something in it that we're not seeing here.

Well, for the simple purpose of echoing a name to a SplashScreen, you wouldn't even need the lookup if the purpose of the login was not for security, but just to get the name for the SplashScreen. But, if you wanted to control the level of access or track the login user, then it would be more...

Ahhh, that makes a lot more sense. I was certainly going down the wrong road if that is what he meant. Maybe he'll log back on and clarify.

I don't see why? I use the same method to autofill a form using a dropdown box. Only one field is bound - yet I can autofill any or all the fields in the record based on the query that calls the combo by referencing the correct column. I would really appreciate your thoughts as we all learn...

Go to the database window, choose Modules, then New. In the open window type Public CurrentUser As String Then save the module with a name of your choosing. What you have done is created a global or Public Variable. Then in the login form use the login to capture that name with a textbox...

Maybe I'm missing something here, but why does it matter if the field is bound or not? The autocomplete (autofill) action could be based on a simple VBA construct like below ... Me.LastName = Me.CboBaseData.Column(1) Me.FirstName = Me.CboBaseData.Column(2) Me.BdAge = Me.CboBaseData.Column(3)...

I think the easiest way would be to create a Global (public) variable called something like CurrentUser. When you log in, it would assign the current user variable name to the login name, then you could use that on the SplashScreen. You could also use it to create a log of who was on the...

You can put a textbox in the header, then =[First Name] & ", " & [Last Name] * note: It's not a good idea to put a space in the fieldname. ClientFirstName and ClientLastName would be better.

It seems to me that he is using his query as the recordsource. (maybe) But if he is, where is the field Client Name coming from? It doesn't match any field in the table.

Bob, maybe you could include a small sample db in the Examples db section. I answered a similar question just a few days ago. It seems like this is a common problem when trying to sum numbers in a main form from a subform.

I know, Bob. It boggles the mind, doesn't it? Someone can actually go to the Advanced Search feature - type in a few key words and get all those answers. Absolutely AMAZING ;) I might even try that sometime.

I did a quick search using "update combo after entry" and got about 20 responses back for it. Hmmmm.

I had to do this at work not long ago (that's what got me back into Access initially) The employees had been entering data directly into tables for so long that they were VERY resistive to using a form instead. But, being the manager, I was able to force that on them despite their...