[AccessD] Need to access EDI Audit Trail (Flat File) and Not Allow Updates

Stuart, Rusty, Jack,

Thanks for your ideas and insights.

For the near term, I am planning to employ a second (behind the scenes)
file.

For the long term, I may use a linked table as I was finally able to get
Access to treat the one large field as a memo field.

Another approach that I spent a little time on is to fire up Internet
Explorer to display the flat file data as it cannot update the data in
the file.

Thanks again for the help.

Brad

   

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jack
drawbridge
Sent: Thursday, November 29, 2012 3:13 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Need to access EDI Audit Trail (Flat File) and
Not Allow Updates

Brad,, I don't really  know how to do what you're asking, but just
thinking
as I'm typing here---
Since anyone who wants to see the Log would only be interested in what
is
currently in the log (available up to the time they make a request),
they
really don't have a need to see the "Log file" per se. They could be
shown
a Read Only copy (from the instant they make the request so to speak) --
and leave the real Log for continued system/processing activity.

So if they were to get to the LogCopy, and alter the attributes from
readOnly  and then alter some data-- they are still working with a copy.

I don't know if that helps, but does keep them from the
"production/active"
log.

Anyway, that and a $1.80 might get you a coffee..

Jack

On Thu, Nov 29, 2012 at 1:35 PM, Brad Marks
<BradM at blackforestltd.com>wrote:

> All,
>
> We have an EDI application that has been built with Access 2007.  It
> works nicely.
>
> Recently there has been a request to add a new feature to the system
> that will allow the users to see the generated EDI audit trail file.
> This is a flat file.
>
> I have added a button to the main form to open the Audit Trail file
with
> notepad.  This works fine, except that now there is a possibility that
> the users could accidentally change the data in this file.
>
> I don't think that I can set security to overcome this issue, because
> the EDI Application adds records to this Audit Trail file (behind the
> scenes).
>
> I thought that another possible solution would be to treat the Audit
> Trail file as Linked Table in Access.
>
> The catch is that the fields in the records are not delimited and the
> records can be over 256 bytes.
>
> Is there a way to tell Access to treat the records as one big memo
> field?
>
> Maybe there is another way to handle this situation.
>
> Thanks,
> Brad
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.