Great!
Add the fields to the form and use the Suppress Condition to hide them when the field has a null value.
HTH,
Brian
Add the fields to the form and use the Suppress Condition to hide them when the field has a null value.
HTH,
Brian
--- In vantage@yahoogroups.com, "richter_clements" <richter_clements@...> wrote:
>
> IT WORKED!!! Thank you so much to those who helped me out....
>
> I see there is a difference between just using 'customize' and actually adding a visual basic form....I added the visual basic form to the CUSTOMER table and it does flow through to the INCHEAD table upon creating invoices allowing me to add to ARFORM...Beautiful!!! Now if I could only add the VB field and the text field (label) if needed....(when VB field is populated...)
>
> This was my very first VB and/or customization. What I learned will help me with many other ideas I have for down the long road to come. Thanks again!!!
>
>
> --- In vantage@yahoogroups.com, "Brian Stenglein" <bstenglein@> wrote:
> >
> > The field would be in the INVCHEAD.DBF, not CUSTOMER.DBF. If you look at the tables used in the Invoice Form, the Customer Table isn't one of them. I know it's not intuitive, but the creation of the DBF files during printing will sometimes pull related data from other tables, like the customer table, and include it with the Invoice Header fields. If you look in the INVCHEAD.DBF, there should be a field that starts with CM plus the external name you gave it. It definately works, I'm doing it.
> >
> > By the way, this thread helped me with a problem I've run into at work, so I have to thank you for stirring up some thoughts that I hadn't used in a while!
> >
> > For my problem, I needed some info from a Packing Slip table to show up on the Invoice. I had previously tried to use a Ship Header VB Form field and it doesn't get written to the INVCHEAD.DBF, but if I put the data in the Ship Detail VB Form, that does get written to the INVCDTL.DBF.
> >
> > Brian Stenglein
> > Clow Stamping Co.
> >
> > --- In vantage@yahoogroups.com, "richter_clements" <richter_clements@> wrote:
> > >
> > > It didn't work. I cleared out temp directory and re-print an invoice...still only about 5 fields in Customer.DBF ...I believe this is a DBF created during the invoice process and nothing to do with the customer master....the customer info on the invoice must be pulled from the Sales Order Header info or somewhere else....and/or only a few fields are being 'passed through' to the temp Customer.DBF....Based on CUSTID - I would like to be able to add the new CHARACTER01 field....to the ARFORM.....I thought the hard part would be adding the field to the actual database - that was the easy part!!! Any other ideas how to easily go about adding this?
> > >
> > >
> > >
> > > --- In vantage@yahoogroups.com, Todd Caughey <caugheyt@> wrote:
> > > >
> > > > First run the bit that creates the DBF file. Print preview is sufficient. Then in Crystal verify the database (under Database on the menu bar). The field should then show up in the appropriate DBF file with a name something like ARUDCHAR2.
> > > > -Todd C.
> > > >
> > > >
> > > > ________________________________
> > > >
> > > > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of richter_clements
> > > > Sent: Tuesday, May 26, 2009 3:16 PM
> > > > To: vantage@yahoogroups.com
> > > > Subject: [Vantage] Vantage 6.1 - how to add a user defined field in Customer master to ARFORM
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > I have been able to make use of character02 in the cusomter master and would like this to print on the ARFORM.. When I open the report in crystal the 'CUSTOMER'.DBF does not show this field as available to add....I'm assuming this DBF file is created during the 'print invoice' process but don't know how to pass along the added field....If I try to add the database from using ODBC connection it tells me this database already is linked by another alias....Also - it is linked via INVNUM (an INDEX) that must be created during the creation of the temp DBF file....
> > > >
> > > > Any suggestions?
> > > >
> > >
> >
>