Re: One Form 2 Another and Check
- From: "Charles L. Phillips" <tptbusines_2205@xxxxxxxxxxx>
- Date: Sun, 9 Oct 2005 15:19:56 -0700
Hello,
"Tank" you are hitting the nail on the head, pitching dollars not pennies,
flying with eagles & not running with turkeys... You are absolutely right!!!
First, let me say, I was not discarding Jeff or Douglas... I just needed
someone with MORE experience to validate my logic in this approach.
Tank everything you pointed is 97.9999% correct. How did you know???
The company is getting new potential customers from canvassing, phones call,
internet surveys & etc.
As for as "potential customers", that have been in the database an over
extended time, but have not become customers, I leave that status up to the
client, and will build into the database how they want that information
handled...
Thank you,
Charles L. Phillips
"Tank" <Tank@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B5F49346-675F-4939-8A6C-DAF4DC6A0206@xxxxxxxxxxxxxxxx
> May I provide another view of this question? Jeff and Douglas are right
on
> track. I'm making an assumption that you may have inherited this database
> and are familiar with pre-existing forms in this database. The data that
> users view in both the CUSTOMERS form (used to view, edit, or enter dew
data)
> and the MAILING LIST form are actually stored in the same underlying
(record
> source) table which identifies personal information about PERSONS
(individual
> customers or potential customers or contact persons representing
> organizations that your firm is identifying as customers or potential
> customers). This table probably has a long list of fields identifying
name,
> address, telephone/fax/email infromation, etc.
>
> As Jeff suggested, the master table should have a field marked as
something
> like "Customer_YN" (a yes/no field). Each of your two forms, CUSTOMERS
and
> MAILING LIST, has a query using the same master "PERSONS" table. In the
> CUSTOMERS query, you will check, "yes" in the field, "Customer_YN". When
you
> run that query, Microsoft will provide you only those records (PERSONS)
where
> the "Customer_YN" field is checked off as "yes". I'm assuming your sales
> people, in talking directly with persons in the MAILING LIST, will check
off
> "Customer_YN" when they make a sale from the potential customer in the
> MAILING LIST.
>
> The MAILING LIST form that the sales people use to make their calls to
> potential customers is based on a second query using the PERSONS table
where
> the the "Customer_YN" field is filtered by your writing in "No" (instead
of
> "YES").
>
> If you do not have sales persons making direct calls to prospective
> customers but simply depend on mail orders to come in, someone will have
to
> enter the MAILING LIST form to check "Yes" for the new customers. But I'm
> assuming you're getting new customers either from new orders or direct
calls.
>
>
> So, with all that said, your MAILING LIST form will only show potential
> customers, while your CUSTOMERS form will show only customers --- based on
> the "Customer_YN" field being either checked off by staff as either "yes"
or
> "no".
>
> To address your other concern about producing a report of new entries, you
> can create a REPORT with the same underlying query for the MAILING LIST.
> Your "PERSONS" table should have an automatic "CreateDate" field providing
> the date the record was created. You can sort the output data in your
> MAILING LIST REPORT in descending order, so that the latest ("new")
entries
> (potential customers) are at the top of your list. The list, of course,
will
> not show "customers", only the potential customers. This list in the
REPORT
> (as in the FORM) will provide all potential customers from "Day 1". To
limit
> the list, you can set the CreateDate field in the query to display all new
> records with a time frame, such as the last seven calendar days. You can
> otherwise control the date range by inserting a phrase in the CreateDate
> field of the query for the REPORT, such as "BETWEEN [Enter beginning date]
> AND [Enter ending date]".
>
> You suggested that the REPORT be produced "automatically", which can be
done
> as you suggested, shortly after the individual opens the MAILING LIST
form.
> I won't go into details now with how that can be done, but a better way
would
> be to have a control button on either the MAILING LIST form or the MENU
form
> preceding the MAILING LIST form that, when clicked, would produce the
REPORT.
> The person producing the REPORT would respond to the pop-up dialog box,
once
> he/she clicks on the control button to open the report for print/preview,
> "Enter beginning date" followed by "Enter ending date". The REPORT
produces,
> in descending order, the "new" entries (records) fitting into the date
range
> specified.
>
> Another issue to address are the records in the master PERSONS table of
> those persons who remain long term as "potential cusotmers", never
reaching
> the CUSTOMER status. At some point, you will of course want to archive
these
> contacts or simply delete them from the table if the information in those
> records becomes obsolete or forever unproductive.
>
> Well, this has been a mouthfull, but I hope it offers some clarity, or at
> least something for you to think about when studying Jeff's and Douglas'
> helpful comments in how to tackle your problem. Perhaps Jeff or Douglas
can
> amplify, and of course, I'd be glad to clarify, as I'm sure further
> discussion may be in order.
> --
> Tank
>
>
>
> "Charles L. Phillips" wrote:
>
> > Hello,
> > I am using MS-Access 97.
> > I have created 2 forms:
> > 1. frmCustomers
> > 2. frmMailingList
> >
> > The frmCustomers is used to send brochures, data, marketing info,
promotions
> > & etc.
> > The frmMailingList is used to store entries of potential customers for
> > future business.
> > Information is sent to members in the frmMailingList. Once a member or
group
> > of members buys products or services, they are considered customers.
> > I need a button/process or technique that allows me to automatically
move
> > data (member or group of members) from the frmMailingList to the
> > frmCustomers... Then I need a button/process or technique, that
> > automatically checks the frmMailingList for NEW entries at 5 minutes
after
> > Startup & print that data, every Thursday...
> >
> > I know I'm asking alot, but can/will someone point me to in the right
> > direction or some sample code...
> >
> >
> > Thank you,
> > --
> > Charles L. Phillips
> >
> >
> >
.
- References:
- RE: One Form 2 Another and Check
- From: Tank
- RE: One Form 2 Another and Check
- Prev by Date: Re: Forms, subforms and embarrasment
- Next by Date: Calender style form
- Previous by thread: RE: One Form 2 Another and Check
- Next by thread: Re: One Form 2 Another and Check
- Index(es):
Relevant Pages
|
