Not at all.  The methods talked about below will work but I don't think
they are necessary for what you want to do.  If the SSANs are stored in
the database with the dashes and you want to accept an SSAN from the
user without dashes and use it for a criteria, the following query
should work.  To use this, create a new query, switch to SQL view and
paste the SQL below into the window.  Change the table names and field
names to match your database then switch back to Design View to test.

SELECT Member.[Participant SSAN]
FROM Member
WHERE (((Member.[Participant SSAN])=Left([SSAN?],3) & "-" &
Mid([SSAN?],4,2)
& "-" & Right([SSAN?],4)))
WITH OWNERACCESS OPTION;

----- Original Message -----
From: Kristen K Smith <[log in to unmask]>
To: <[log in to unmask]>
Sent: Monday, October 16, 2000 7:49 AM
Subject: Re: [PCSOFT] Parameter queries in Access


> The table was originally created with the dashes stored, so on forms,
> reports, etc.  the dashes do show up.
> And naturally, because they are stored, they do need to be included in
the
> parameter prompt in order for
> Access to find a match.  It looks like I will have to create a form if
I
> want the dashes to appear automatically,
> as it doesn't seem to be possible to format the parameter query box in
this
> version of Access ... with luck
> maybe Microsoft will include this in the next upgrade.  Thanks again!
>
>
> From Earl Truss >>
>
> <<I can help with this.  Is the Social Security Number stored in the
> database formatted with the dashes or is it stored only as the
digits?>>
>
> <<You should be able to accept their input into a parameter without
dashes
> and compare it against a copy of the SSN where you have removed the
> dashes from the database copy.>>
>
>
> From Jim Meager >>
>
> <<You need to modify the SS field's format in the TABLE to include the
> dashes.
> Once the table is saved, the dashes will automatically "ripple"
through
> to all forms and reports.>>
>
>
> From Mike Buraczewski >>
>
> <<Create a form.  On the form include a combo box to select the social
> security number from and include a calendar control to select the
date.
> Add
> a button to print the report [the wizard will work to set up the
code], and
> a button to preview the report if your user would like to see the
report
> but
> not necessarily print it.>>
>
> <<In the query, you can change the criteria that is forcing the user
to
> enter
> the social security number and date to:
> forms!myNewForm[cboSSNum] and the date criteria to
> forms!myNewForm[actXCal]>>
>

                Curious about the people moderating your
                   messages? Visit our staff web site:
                     http://nospin.com/pc/staff.html