On 15/10/06 23:38 +0530, Saswata Banerjee & Associates wrote: <snip>
But please understand that it allows you to manipulate the data by putting in entries in the middle. That makes the program unsafe from the owners perspective. There is no data integrity. There is no guarentee that the data you see now is the same as the one you saw earlier.
Quoting myself:
That is precisely why most SMEs like Tally. Accountants like Tally because they can input data quite fast.
SMEs like Tally because they _can_ manipulate accounts without a trace.
<snip>
X will work in the office. How will you connect multiple offices to the same database ?
X is already network capable. You application is an X client, and speaks to the X server. X can be tunneled over ssh, or the client application can run locally and talk to a remote database, preferably over a VPN. If you want a Windows analogy, think MS-SQL server as the backend, not MS Access or a flat file like Tally.
And how will you allow the owner to access the data from outside the office (say from his home).
X, VNC, NX.
Will you allow an user from outside the office to log into X ?
a) The user has an X server, and uses a VPN or ssh to access the data and runs the app remotely. b) The user has a VNC client, and connects to a remote VNC server. c) The user runs a VNC applet in a browser. b) The user uses NX to connect to the remote server and gets a full desktop.
How much bandwidth do you need from working from outside the office ?
I have successfully used X over dialup at 33.6 kbps. I have seen NX being used (slowly) over GPRS to view a full KDE desktop.
Not using a heavy widgetset allows for good network performance.
Devdas Bhagat