[AccessD] Sort of like a filter only not

No, but if I encrypt (ie scramble in a structured way) then I can unencrypt
that one and encrypt another customer afterwards.

Andy


> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of 
> Gustav Brock
> Sent: 13 December 2003 12:02
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Sort of like a filter only not
> 
> 
> Hi Andy
> 
> I see. But my idea wouldn't work if the sales person was 
> visiting several clients per day - except if all customers 
> were scrambled and he brings a list telling which real 
> customer, say, "McAllen & Daughters Ltd." represents.
> 
> /gustav
> 
> 
> > Not sure what you mean by "mixed up" Gustav. Take one of 
> many screens. 
> > Here you can select a financial period and year; select a 
> customer or 
> > a customer group or leave blank for all customers, hit Print and a 
> > report will show the orders for those criteria, a summary of 
> > expenditure, render it into GBP if it was export and so on. 
> And that's 
> > just one of many, many examples. Now the pitfalls are that a) the 
> > sales person may/will drop down the combo to choose the customer, 
> > thereby showing other customers or b) may inadvertently select the 
> > wrong customer and print the report (and hand it over to his client 
> > before he realises his mistake - aargh!) or c) hit Print without 
> > selecting a customer and therefore list activity for all customers. 
> > This is the sort of thing I'm talking about. And as I 
> stressed right 
> > from the start there are oodles of such situations in the system so 
> > attacking each one individually is not an option.
> 
> > At the moment I like your idea Gustav of deliberately 
> "corrupting" the 
> > rest of the data so that it's there but unrecognisable. If 
> I did that 
> > to selected fields (names, addresses, phone nos, email 
> addresses and 
> > so - not too many I don't think) I think that would do 
> nicely. I guess 
> > I could even do it by encryption so that it's reversible. 
> That way my 
> > on-the-road salesperson could "corrupt" all but one customer, then 
> > un-corrupt all after first meeting and re-corrupt all but a second 
> > customer when they get to the next place.
> 
> > --
> > Andy Lacey
> > http://www.minstersystems.co.uk
> 
> 
> 
> 
> > --------- Original Message --------
> > From: "Access Developers discussion and problem solving" 
> > <accessd at databaseadvisors.com>
> > To: "Access Developers discussion and problem solving" 
> > <accessd at databaseadvisors.com>
> > Subject: Re: [AccessD] Sort of like a filter only not
> > Date: 12/12/03 13:44
> 
> 
> > Hi Andy
> 
> > Hmmm ... but why are the data initially mixed up?
> 
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com 
> http://databaseadvisors.com/mailman/listinfo/a> ccessd
> Website: 
> http://www.databaseadvisors.com
> 
>