That is a thought, why are they exporting and can their work be done
in TinyERP instead.  Every time a user asks for data outside you need
to ask some questions.

1. Is this a recurring need?
2. Do I need to support the data after it is out?
3. Is the data being requested the correct data for the need/goal?
4. Will changed data be requested to be uploaded?




On 4/8/07, pedro <[EMAIL PROTECTED]> wrote:

Thanks for the reply. Unfortunately this won't help much in this case. I know I 
can use SQL directly on the database, however, using TinyERP export 
capabilities I can assure that the rest of the users can also retrieve the 
information without much hassle. Also, they will be able to export only the 
data that they are allowed to browse. If I let them use SQL I will have to 
bother with permissions at the database level and this is something I don't 
plan to do.

However you give me an idea: construct a new tinyerp class based on a view with 
the relevant fields and let the users browse those... mmmm... maybe...

Thanks anyway for your reply,
Pedro





_______________________________________________
Tinyerp-users mailing list
http://tiny.be/mailman/listinfo/tinyerp-users



--
---
Andrew Latham - AKA: LATHAMA (lay-th-ham-eh)
[EMAIL PROTECTED] - [EMAIL PROTECTED]
If any of the above are down we have bigger problems than my email!
Hind sight is most always 20/20 or better.
---
_______________________________________________
Tinyerp-users mailing list
http://tiny.be/mailman/listinfo/tinyerp-users

Reply via email to