...
OK, DCFusor will not be impressed, but there are LOTS of fairly tricky ways of encrypting data (emails and sales data for example) that would stand up to almost anything except skilled cryptologists with good computers. Here is some SQL coding (for MS Access, oh, sorry again DCFusor (does not like Access)), your SQL will vary if you use other SQL databases (like Oracle, MySQL, etc.):
SELECT DISTINCTROW (((Right(([df_2].RUC),2) Mod 2) + 1) * 10) & (Right(Left((([df_2].RUC) * 599),11),10)) AS Cust_ID, (Right(Left(([df_2].Cliente),4),1)) & (Left(Right(([df_2].Cliente),3),1)) & (Left(Right(([df_2].Cliente),2),1)) & (Right(Left(([df_2].Cliente),4),1)) AS Customer, Sum([df_2].Cant) AS Sum_of_Qty, Sum(CCur([Cant]*[VUnit]*((100-[Dscto])/100))) AS Expr9
FROM df_2
WHERE RIGHT(([df_2].Fecha),2) = "13"
GROUP BY [df_2].Cliente, [df_2].RUC;
That nasty-looking coding cannot be explained very easily, but there are some cool functions (prime number 599 (although that is NOT the real number), a Modular function and manipulating text around to hide customer names (this last is rather weak though) in there that I use to protect the real data.
Here are two rows of output (ahh, well that did not format well in my Cut & Paste...), first are the field names, then the columns. Note that customer "DEMA S.A." is identified here (and so has six items of text here, that period/dot in "position two" is derived from the above SQL and is deliberate).
Cust_ID
Customer
Expr9
RUC
Cliente
Expr9
201149974507
T E
$3,408.61
100347361191
.
$3,306.45
20101177042
DEMA S.A.
$3,306.45
More details at my new blog piece (as I know the above is "Pure Greek"):
http://tinyurl.com/kkdath3