goto record in query based on textbox value

[Becker]

I have a form "Finish" which has a record source "finish query". Criteria for the query is that they must enter an item # to view only that record at that time. I want them to be able to just type the item # into a text box to view that record without having to close and reopen the form. I don't want the records to be editable and I don't want users to be able to scroll through records at the bottom of the window either.

I don't know if its possible but I would also like to do this with two different queries on the same form. The second being where they type a hood # to view a record.

[zmbd]

Start with these two threads:

Example Filtering on a Form. (this is also linked to in the following thread....)

discussion between Rabbit and myself about the merits of VBA versus Form/subform

Controls and forms can be locked/enabled etc in their properties box and the available default controls set from there too at the form level.

-z

[zmbd]

Becker
I noticed that you have very few posts and I took the time to read thru them...

You might find the following links useful to read thru:

Database Normalization and Table Structures. This article does a fairly good job explaining the normalization concepts - I was a very good refresher for me when I read it.

This website has a great basic tutorial on RDMS design... A Tutorial for Access

Of particular note is tables page within the tutorial:

- When describing the table, notice how and what information is given by the author, the table name, the field name, the field type, key or index, etc... When you post back about tables, this is the type of information we'll need to help you along in your project. You don't need a fancy gridded table to do this as in the article... just a line by line layout... and you can use the [CODE][/CODE] tags to group each table if you want to get fancy ;-)

As for lookup fields in tables... I avoid lookup fields at the table level! :Are Lookup Fields in Tables Evil? ... despite the fact that these are supported in MSAccess, they are not supported in other databases should you need to upgrade and writing queries later on will be somewhat problematic.

IMHO: The ONLY exception to table level lookup fields I've seen for this deals with a share-point integration.

There will be other people that argue that these are just fine at the table level (and people argue about DAO v ADO design too... IMHO depends on the application and if upsizing is desired latter) ... I side with with the MVPs that do this stuff for a living... they don't like them

-z

[Becker]

Thanks again for your help. This is very valuable information for me.