Jan:
I have one application with this ability.  The structure was started by another 
programmer, so I don't take full credit.  It isn't perfect, as we added 
features over the years and would've done it differently if I had designed it 
today. 

Here's the structure of the table (not all the columns), along with a 
description of what some of the columns are for.  We have a scheduled task that 
runs every 20 minutes, scans the table for "xDateTimeSent is null".  Cursors 
thru the rows, sends out using RMail, updates the xDateTimeSent.  The program 
that deciphers all the elements is quite complicated.

It was originally set up to send emails to "groups" (ReptGroup).  There's a 
maintenance table that has a group name and a list of email addresses.  So 
different programs will send emails to different "groups" of people (a group 
could have just one person).  Later on, we needed the ability for users to send 
emails to specific people, not a group, so we created an AlertDetail table that 
has the to / from / cc information.
It works really well for us.



  Table: Alert                

CmdFile            Type   : TEXT 50   This is the name of the RBase program 
that created the email
ReptGroup          Type   : TEXT 8
   The group the email is sent to; lookup to another table for email addresses
xDateTime          Type   : DATETIME NOT NULL   When the email was inserted
xDateTimeSent      Type   : DATETIME   When the email was sent by RMail
AlertSubject       Type   : NOTEAlertFailed        Type   : DATETIME   If RMail 
failed, date put here
EmailTypeID        Type   : INTEGER    Default: 1   1 = look at ReptGroup, 2 = 
look at AlertDetail table for email address
AlertEmailType     Type   : TEXT 4     Default: TEXT
   This was added when we started using HTML as the body on some emails.  Would 
have the word "HTML"
AlertFileAttach    Type   : TEXT 120   Name of a file to attach
AlertNote          Type   : NOTE
   If the email body is just a string text, it goes in here
AlertTxtFile       Type   : TEXT 120   Or the email body can be contained in an 
external file, either ascii or html.  So this would be the filename, like 
F:\EmailFiles\Orders.txt
 
 Hope this gives you some ideas!!

Karen

 
-----Original Message-----
From: jan johansen <j...@jjcalibrations.com>
To: rbase-l@googlegroups.com
Sent: Wed, May 4, 2022 10:03 am
Subject: [RBASE-L] - eMail table structure

Greetings, Was just wondering if anyone had a successful table structure to 
store emails to send, etcthat would be willing to share. TIA, Jan-- 
For group guidelines, visit 
http://www.rbase.com/support/usersgroup_guidelines.php
--- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbase-l+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbase-l/WC20220504150311.87010F%40jjcalibrations.com.

-- 
For group guidelines, visit 
http://www.rbase.com/support/usersgroup_guidelines.php
--- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rbase-l+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rbase-l/1649618192.3458901.1651683163487%40mail.yahoo.com.

Reply via email to