> On Tue, 15 Oct 2002 10:16:44 +0800, you wrote: > >On Tue, 15 Oct 2002 01:08, Elizabeth Ziph wrote: > >With SL one can visit a client, perform a service, and from the client's > >office, befor leaving, record the transaction, print an invoice, exact and > >record payment. > > > >So, security is important, and so is undestanding whether (and why) the > >transactions can be done securely.
In the old SQL-ledger, the documentation advised users to set certain things globally read-writable, though I understand that has been changed now. At that time, I had to tell my partner not to give system accounts because of that. I do find SQL-ledger over https very useful. I had set it up for a client so he can access it at trade shows, even though he's not advanced enough to have it set up as a laptop. There's other hidden potentials, too, because if the security model does get more sophisticated -- and I mean, if you set up an SQL ledger and restrict that user to Read-Only, and has no access -- not even readable access -- to the parts you don't want the person to see, you can easily create a customer access point. Such customer would be able to see the number of invoices outstanding. Or, you could hook it up with an ecommerce package and let the customer see the information from that point. It's something that I've been working on with my setup, which I'm adding that project tracker, and a few other things to feed into there. -Qaexl- http://www.next-horizons.com/qaexl/ ------------------------------------------------------- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm ------------------------------------------------------- (un)subscribe: http://lists.sourceforge.net/lists/listinfo/sql-ledger-users Archive: http://www.mail-archive.com/[email protected]/
