[6.1] Customer Required Specs on POs to Our Vendors

Here's another Idea, determine a max size you use for your part description
(say 35 characters) The as Lydia suggested, put your specs in the extended
part description. Then created a calculated field using MID( string, 35,
255). This would pull out the next 220 characters of description into its
own field that you can place anywhere on your form.

Shirley

_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Lydia Coffman
Sent: Friday, September 02, 2005 11:27 AM
To: 'vantage@yahoogroups.com'
Subject: RE: [Vantage] Re: [6.1] Customer Required Specs on POs to Our
Vendors

Just a thought here -- what about the extended description of the part?
Are you already using that for something else? Seems like you could open
that description up on the PO (to 5 lines or whatever)and truncate it if
there is nothing in there.

Might be worth a try.
Lydia


-----Original Message-----
From: Brian Stenglein [mailto:bstenglein@...]
Sent: Friday, September 02, 2005 8:19 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: [6.1] Customer Required Specs on POs to Our
Vendors


Todd,

Couldn't you enter the verbage in the Customer VB form field and add
a subreport with JobProd, OrderHed, and Customer tables? The
subreport would be linked by the Job # in JobProd to the Job# in
PORel.dbf.

Brian Stenglein
Clow Stamping Co.

--- In vantage@yahoogroups.com, "Todd Caughey" <caugheyt@h...> wrote:
> They are the same for every part for that customer (part to
customer is 99% one-for-one relation here as I expect it is for you
too). Preferable would be to trigger block of specs on PO to our
vendors for any job related to that customer - for all parts. But if
there is a way to code the specs on the parts we can live with that
as being easier to remember to do than job notes on each job (as we
are doing now and often forgetting). I was really hoping there was
some table somewhere that I have been missing that carrys at least
part specs through to the PO or worst case I can grab with ODBC.
>
> Another thought......maybe I will create DBFs with PO print preview
and have a distributed report for each customer that has the specs
bolted in as an .bmp image file the user can maintain with Windows-
Paint. We only have 5-6 such customers. This would suffice until we
eventually get to 8.0.
>
> Thanks,
> -Todd
>
> -----Original Message-----
>


Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have
already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and
Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
<http://groups.yahoo.com/group/vantage/files/>
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/links



_____

YAHOO! GROUPS LINKS

* Visit your group "vantage <http://groups.yahoo.com/group/vantage> "
on the web.

* To unsubscribe from this group, send an email to:
vantage-unsubscribe@yahoogroups.com
<mailto:vantage-unsubscribe@yahoogroups.com?subject=Unsubscribe>

* Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
<http://docs.yahoo.com/info/terms/> .

_____


Tracking #: EDCDCAE343CEA74A83404545F4CC8BDE18E4692E


[Non-text portions of this message have been removed]
Just a thought here -- what about the extended description of the part?
Are you already using that for something else? Seems like you could open
that description up on the PO (to 5 lines or whatever)and truncate it if
there is nothing in there.

Might be worth a try.
Lydia


-----Original Message-----
From: Brian Stenglein [mailto:bstenglein@...]
Sent: Friday, September 02, 2005 8:19 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: [6.1] Customer Required Specs on POs to Our
Vendors


Todd,

Couldn't you enter the verbage in the Customer VB form field and add
a subreport with JobProd, OrderHed, and Customer tables? The
subreport would be linked by the Job # in JobProd to the Job# in
PORel.dbf.

Brian Stenglein
Clow Stamping Co.

--- In vantage@yahoogroups.com, "Todd Caughey" <caugheyt@h...> wrote:
> They are the same for every part for that customer (part to
customer is 99% one-for-one relation here as I expect it is for you
too). Preferable would be to trigger block of specs on PO to our
vendors for any job related to that customer - for all parts. But if
there is a way to code the specs on the parts we can live with that
as being easier to remember to do than job notes on each job (as we
are doing now and often forgetting). I was really hoping there was
some table somewhere that I have been missing that carrys at least
part specs through to the PO or worst case I can grab with ODBC.
>
> Another thought......maybe I will create DBFs with PO print preview
and have a distributed report for each customer that has the specs
bolted in as an .bmp image file the user can maintain with Windows-
Paint. We only have 5-6 such customers. This would suffice until we
eventually get to 8.0.
>
> Thanks,
> -Todd
>
> -----Original Message-----
>