By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,478 Members | 1,665 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,478 IT Pros & Developers. It's quick & easy.

Issues with Parameter Query Subform in Access 2003

P: 2
I'm a relative newbie to Access, working in 2003 and trying to build a very simple client database for my company. Here's the basic set-up I have so far:

-Clients Table contains all the relevant contact info for all clients. Name, address, email, contact person, etc.
-Orders Table contains each order the various clients have made, including dates, quantities, etc.

The Orders table contains a Client ID field that links it to the Clients table. The trouble is right now you have to open the Clients table and scroll through it to find the ClientID for each order, which is silly and time-consuming. I created a parameter query that returns the ClientID when you search any part of the client name, but I ran into trouble when I tried to embed it as a subform in the Order entry form. (In my ideal world, users would open a single form (with subforms, obviously) to look up a client's ID and enter their order info.) I want users to be able to re-enter the parameter if they mis-type something or have more than one order to enter in a sitting, but can't for the life of me figure out how to get the prompt window to re-open without closing the form entirely and reopening. Not actually sure if it's possible or not, so any solutions regarding entering new parameters without closing and reopening forms would be greatly appreciated.

I am not very familiar with VBA, but can figure it out if given simple and concise instructions.

Thanks!
Nov 14 '11 #1
Share this Question
Share on Google+
3 Replies


NeoPa
Expert Mod 15k+
P: 31,709
It sounds like you've gone off in a few wrong directions I'm afraid.

The first thing I would say is to explore a little first using the wizards. The items they create often indicate what is possible and easy with Access. Many people come into the subject with existing thoughts about how things should work and often miss the point of how Access does things. This is extraordinarily debilitating as far as their development and progress goes.

Next I'd say look at the concept of Database Normalisation and Table structures. This is less directly connected to the question but probably needs to be looked at first.

As a hint (I don't believe you're in a position yet to take basic instructions on this) an orders form would normally have a ComboBox control whose list data is populated from the [Clients] table, but whose selected value (which is normally an automatically generated numeric ID field even if the data displayed might be a client name) is stored/saved in a field within the [Orders] record. It's important to perceive how and why this would work for your requirement.
Nov 14 '11 #2

P: 2
Boo. A disheartening answer, but I appreciate it. I'll explore the links you've provided to see if I can find a better approach to the issue.

Thanks.
Nov 14 '11 #3

NeoPa
Expert Mod 15k+
P: 31,709
Sorry to dishearten. Access is not as pick-up-and-go as MS would have you believe, but with some intelligence it's achievable. Your mistakes and thinking only reflect inexperience so far. Nothing to be disheartened about from that perspective.

Remember, you can always ask questions. The smaller and more distinct they are the easier it is for you to get an answer. Another point well worth remembering. Good luck.
Nov 14 '11 #4

Post your reply

Sign in to post your reply or Sign up for a free account.