Replies

This is, unfortunately, something that I’ve got to get working, but I didn’t create myself. The ‘master’ record has an autonumber field, which is used as a key into the subservient tables. Why they weren’t combined into one master record, I can’t really say. But suffice it to say that I have to get it working. If there’s not an easy way to gather up the fields and perform an ‘Add these fields to a Record in table X’, then I’ll see if I can get the tables put together into bound fields on the main form. Either way, it will be an interesting exercise, and one which I don’t have the luxury of boundless time.

Yes, that’s exactly what I meant. I split the database before I realized the implications. And, having never used a split database, I was unfamiliar with exactly what happens. Needless to say, it was an eye-opener. I’ll modify the back end links, and be sure to turn on referrential integrity. Thanks for the quick update.

Thanks, however I think I found a different way. Access is still new to me, but I can do VB. I finally located the DLookup method, and it gives me what I wanted.

I do appreciate the fast reply.

Brian

It was the second item you mentioned. Thanks!

Brian

Keydown is exactly what I’m trapping. Not only can the user enter the date in numerous formats, but it makes changing the date extremely simple. I was surprised how elegant it makes the app look.

Definitely using four digits for the year! Thanks for the tip.

Thanks! That gave me the best of both worlds. I can let the user enter the dates in multiple formats, and still use the +. -, pgup and pgdn functions like Quicken. It should make things easier for our customers.

That’s just what I did. Thanks! With the help of this group, I’ll get through this!

Brian

And therein lies the rub. I have absolutely no idea how to invoke that beastie. I’ve managed to change the field from text to Combo, but the wizard lurks invisibly.

Let’s just say – these people have been filling out forms by hand, and anything like a Combo box would probably scare them.

By the way, that worked wonderfully. I’m on the way to completing this, and without bothering my digestion. Thank you very much!

Brian

Yes – design specifications passed down. It’s one of those “We don’t know how to use that” sort of things.

Well, I’m getting so close I can almost taste it. Here’s the query I’m trying:

Set rs = dbs.OpenRecordset(“SELECT * FROM [Branch Office] WHERE [Office ID]=” & Branch_Office.Text)

The Office ID is a string field.

I added a reference to DAO, but I’m still getting an error – Runtime Error 3061 – too few parameters. Expected 1.

I suspect that something hasn’t been resolved. I’ll keep digging. Thanks!

The keypress event is raised when a key is pressed in a field on a form. With it, I hope to be able to take the current value in the field, and perform a query of Office ID on the table, then display the results in the field on the form. It would in effect, be filling in the field as the user types (similar to the way Quicken fills in fields). It also forces the user to only enter valid data. The result is similar to populating a combo box with the allowable values, then let the user choose the data. Same effect, but the interface looks different.

When the user tabs away from the field, the Field_Exit event is raised, and I will then populate the remaining parts of the form with the fields from the last query.

Perfect! Thanks for the quick assist.

Try this package, which is actually from Microsoft:

http://www.vbdiamond.com/Sources/ViewSource.asp?ID=1182%5B/url%5D

It got me started.

Hyperlinks added- Mod