Hi Jan.  I have a couple of tables that I use for frames, lenses, lots of
optical stuff, so most of it may not suit you, but it's been in use pretty
much unchanged for many years and works quite well:

   Table: i                    No Lock(s)
 No. Column Name        Attributes
 --- ------------------
------------------------------------------------------
   1 ino                Type   : INTEGER  AUTONUMBER             * (key)

                        Index  :
SINGLE-COLUMN
   2 gent               Type   : TEXT
13                                      *(general category)
   3 ment               Type   : TEXT
22                                      *(specific category)
   4 lent               Type   : TEXT
22                                      (even more specific category)
   5 iname              Type   : TEXT
25                                      (brand or generic name)
                        Index  :
SINGLE-COLUMN
   6 ilist              Type   :
CURRENCY                                     *(list cost, my cost)
   7 ava                Type   : TEXT
66                                      availability
   8 mpn                Type   :
INTEGER                                      manufacturer i.d. #
                        Index  :
SINGLE-COLUMN
   9 icmt               Type   : TEXT
66                                      comments
   Current number of rows:   8413


   Table: S                    No Lock(s)
 No. Column Name        Attributes
 --- ------------------
------------------------------------------------------
   1 SNO                Type   : INTEGER  AUTONUMBER
key
                        Index  :
SINGLE-COLUMN
   2 INO                Type   : INTEGER
     foreign key
                        Index  :
SINGLE-COLUMN
   3 EYE                Type   :
INTEGER                                        a size descriptor
   4 DBL                Type   :
INTEGER                                        another size
   5 TMP                Type   : TEXT
10                                         another, but text allowed
   6 CLR                Type   : TEXT
24                                         a color
   7 PRICE              Type   : CURRENCY
our price
   8 cpt                Type   : TEXT
12                                          a code we use now HCPC
   9 size               Type   : TEXT
40                                         a format we use
                        Compute: (clr&ctxt(eye)+'-'+ctxt(dbl)&
tmp)
  10 used               Type   :
INTEGER                                      the number we've sold
   Current number of rows:  15213


View: iv
SELECT T_1.*,T_2.* FROM S T_1,i T_2 WHERE ( T_1.INO = T_2.ino )

When I (finally) migrate to windows, I'll probably dump the ava and cmt
columns in favor of an unlimited comment field in another table, and of
course the "used" column could be generated on the fly from transaction
tables, which are linked into using the "sno" or stock number, depending on
if 9.? is fast enough to do that.



On Mon, Sep 26, 2011 at 11:29 AM, jan johansen <[email protected]>wrote:

>  Group,
>
> It's time for me to replace a very old table or at least revamp it.
> I'm looking for ideas for a PARTS or INVENTORY table (or however you may
> call it).
> Anyone willing to share their favorite .TBL file?
>
> Jan
>
>
>
>
>
> -----Original Message-----
> From: "jan johansen" <[email protected]>
> To: [email protected] (RBASE-L Mailing List)
> Date: Mon, 26 Sep 2011 09:54:58 -0700
> Subject: [RBASE-L] - Re: Cannot use Multiple Addresses in 9.1
> MapiMailPlugin
>
>  Bill,
>
> I believe you are missing the dotted variable on you B
>
> set v vMultiMailTo1 text=(.vMultiMailToA+';'+* vMultiMailToB*)
>
> Jan
>
>
>
>
> -----Original Message-----
> From: <[email protected]>
> To: [email protected] (RBASE-L Mailing List)
> Date: Mon, 26 Sep 2011 09:37:59 -0700
> Subject: [RBASE-L] - Cannot use Multiple Addresses in 9.1 MapiMail Plugin
>
>  I am using rbg9.1-64 latest and pluginpowerpack 91.
>
> I cannot get the mapimail3 plugin to launch with more than 1 name. Is there
> a limitation on the the number of addresses mapimail3 can send ?
>
> Here is my code, can anyone spot an obvious error ?
>
> clear all variables
> set v vInsStart date=08/01/2011
> set v vInsEnd date=12/31/2011
> SET VAR vQuote TEXT = NULL
> SET VAR vQuote = (CVAL('QUOTES'))
> SET VAR vDummy TEXT = 'vDummy'
> SET VAR vPipe TEXT = NULL
> SET VAR vPipe = '|'
> SET VAR vTo TEXT = NULL
> SET VAR vSubject TEXT = NULL
> SET VAR vCc TEXT = NULL
> SET VAR vBcc TEXT = NULL
> SET VAR vBody TEXT = NULL
> SET VAR vAttachments TEXT = NULL
> set v vMultiMailToA text='[email protected]'
> set v vMultiMailToB text='[email protected]'
> set v vMultiMailTo1 text=(.vMultiMailToA+';'+vMultiMailToB)
> set v vMultiMailTo1=.vMultiMailTo1
> SET VAR vQuote TEXT = NULL
> SET VAR vQuote = (CVAL('QUOTES'))
> SET VAR vDummy TEXT = ('vDummy')
> SET VAR vPipe TEXT = NULL
> SET VAR vPipe = ('|')
> SET VAR vTo TEXT=('TO:'+.vMultiMailTo1)
> SET VAR vperiod text=((ctxt(.vInsStart))+'To:'+(ctxt(.vInsEnd)))
> SET VAR vSubject=('Subject:Inspection Report From:'+.vPeriod)
> SET VAR vCc TEXT=('CC:')
> SET VAR vBcc TEXT=('BCC:')
> set v vBody2 text=('Please Review attached Inspection Report.')
> SET VAR vBody TEXT=('BODY:'+.vBody2)
> SET VAR vAttachments TEXT=('Attachments:'+.vfilespec)
> set v vresolve text=('Resolve_Names:FALSE')
> SET VAR vParameters TEXT = NULL
> SET VAR vParameters = +
> (.vQuote+.vDummy&.vPipe+.vTo&.vPipe+.vSubject&.vPipe+.vCc&.vPipe+ +
> .vBcc&.vpipe+.vBody&+.vPipe+.vAttachments&.vPipe+.vresolve)
> PLUGIN MapiMail3 &vparameters
> ret
>
> Thanks,
>
> Bill Eyring
>
>


-- 
William Stacy, O.D.

Please visit my website by clicking on :

http://www.folsomeye.net

Reply via email to