summaryrefslogtreecommitdiff
path: root/doc/faq.html
blob: dc739e0528f95d92dae5aaebaf5187322d253e69 (plain)
  1. <ul>
  2. <li><h4>Printing to a Printer from a Windows Server</h4><p>
  3. There are several obstacles to printing from a web appliction that was written
  4. for Linux or UNIX in Windows.
  5. These include:</p><ul>
  6. <li>Lack of Postscript support in the printing subsystem. To resolve this, you
  7. must install Ghostscript and Gsview. The latter package provides a utility
  8. called gsprint that will allow you to print Postscript on your Windows
  9. printer.</li>
  10. <li>The fact that most Windows software, including gsprint, tends to print
  11. output that will cause the web server to crash. The winprint.bat included
  12. with this distribution corrects this problem. To use the winprint.bat
  13. solution, configure your printers in your ledger-smb.conf as
  14. "winprint.bat printer-name." If you omit the printer name, the default
  15. printer will be used.</li>
  16. <li>Windows does not allow you to set up system printers that all users can
  17. access. Thus the web server often doesn't have access to the printers you
  18. have set up. To correct this issue, follow the steps at
  19. <a href="http://support.microsoft.com/kb/q184291/">
  20. http://support.microsoft.com/kb/q184291/</a>.</li></ul></li>
  21. <p><li><h4>Error on converting from SQL-Ledger:
  22. ERROR: column "chart_id" contains null values</h4>
  23. SQL-Ledger does not enforce a NOT NULL constraint on the chart_id field in the
  24. acc_trans table. Consequently, it is possible in cirtain circumstances to
  25. insert transactions into the database with invalid information including NULL
  26. chart_id's. When this occurs, normally the Chart of Accounts and Trial Balance
  27. will fail to balance. So this is a serious problem with data integrity.
  28. LedgerSMB prevents this by adding the NOT NULL constraing but this can cause
  29. prevent people from migrating when they have invalid data in their databases.
  30. <br/><br/>
  31. If you encounter an error like this, the first thing to do is seek
  32. technical support, regardless of whether or not you wish to continue
  33. the migration. In general the providers of support for LedgerSMB and
  34. SQL-Ledger should all be able to be of some assistance.
  35. Unfortunately, since this problem involves information loss, no
  36. solution can be automated without invalidating your accounting
  37. information. </li></p>
  38. <p><li><h4>PostgreSQL 8.x</h4>
  39. PostgreSQL added a restriction in v8.x that a sequence cannot be dropped
  40. after if it is referenced by a table. However backups created with
  41. LedgerSMB v2.6.13 and earlier have a DROP SEQUENCE step in the backup
  42. which will fail. To fix this edit the backup before restoring on a 8.x
  43. system.
  44. <p>This typically looks like this:
  45. <pre>
  46. DROP SEQUENCE id ;
  47. CREATE SEQUENCE id START 10579;
  48. --
  49. DROP SEQUENCE invoiceid ;
  50. CREATE SEQUENCE invoiceid START 11096;
  51. --
  52. DROP SEQUENCE orderitemsid ;
  53. CREATE SEQUENCE orderitemsid START 178;
  54. --
  55. DROP SEQUENCE jcitemsid ;
  56. CREATE SEQUENCE jcitemsid START 53;
  57. </pre>
  58. <p>Change it to:
  59. <pre>
  60. CREATE SEQUENCE id;
  61. SELECT SETVAL('id', 10579);
  62. CREATE SEQUENCE invoiceid;
  63. SELECT SETVAL('invoiceid', 11096);
  64. CREATE SEQUENCE orderitemsid;
  65. SELECT SETVAL('orderitemsid', 178);
  66. CREATE SEQUENCE jcitemsid;
  67. SELECT SETVAL('jcitemsid', 53);
  68. </pre>
  69. <p><li><h4>PostgreSQL template1</h4>
  70. <tt>template1</tt> is a template that new databases are built from, by
  71. default. Anything you put into <tt>template1</tt> will be copied to a
  72. new database. Thus, when you try to create a new dataset, the tables
  73. are already drawn in from <tt>template1</tt> so that when LedgerSMB
  74. tries to create them, you will receive an error message indicating
  75. that the tables already exist.
  76. <p><li><h4>Japanese characters</h4>
  77. modify apache so that EUC_JP is the main additional language.
  78. <br>comment out all unrelated languages except, UTF_8 shift jis, EUC_JP
  79. <br>restart apache
  80. <br>Fire up psql and do the encoding as per the table:-
  81. <br>Table 5-2. Postgres Client/Server Character Set Encodings
  82. <p>Server Encoding Available Client Encodings
  83. <br>EUC_JP EUC_JP, SJIS
  84. <br>EUC_TW EUC_TW, BIG5
  85. <br>LATIN2 LATIN2, WIN1250
  86. <br>LATIN5 LATIN5, WIN, ALT
  87. <br>MULE_INTERNAL EUC_JP, SJIS, EUC_KR, EUC_CN, EUC_TW, BIG5, LATIN1 to LATIN5, WIN, ALT, WIN1250
  88. <p>Create the dataset from admin.pl, now the Japanese shows up in multibyte encoding
  89. <p>Now you can write in Hiragana, Katakana, Kanji and English
  90. <p><li><h4>Error posting a check/receipt</h4>
  91. <pre>
  92. DBD::Pg::db do failed: ERROR: syntax error at or near "," at character 114
  93. Error!
  94. INSERT INTO acc_trans (trans_id, chart_id, transdate,amount)
  95. VALUES (13314, , '03-22-2005',1.00 * 1)
  96. ERROR: syntax error at or near "," at character 114 </pre>
  97. This error is caused by a transaction which does not have links to
  98. an AR/AP account.
  99. <br>set up your chart of accounts properly and create at least one
  100. AR and AP account. Then edit all your transactions and repost.
  101. <p><li><h4>SELinux</h4>
  102. <a href=http://fedora.redhat.com/docs/selinux-faq-fc3/index.html>http://fedora.redhat.com/docs/selinux-faq-fc3/index.html</a>
  103. <p>modify <tt>/etc/selinux/conf</tt> and set <tt>SELINUX=permissive</tt>
  104. <p>use <tt>audit2allow</tt>, add the following to
  105. <tt>policy.conf</tt>, then run <tt>make reload</tt>
  106. <p>#line 83
  107. <br>allow httpd_sys_script_t port_type:{ tcp_socket udp_socket } { send_msg
  108. recv_msg };
  109. <br>allow httpd_sys_script_t sysctl_kernel_t:dir search;
  110. <br>allow httpd_sys_script_t sysctl_t:dir search;
  111. <br>allow httpd_sys_script_t tmp_t:sock_file write;
  112. <br>allow httpd_sys_script_t httpd_sys_content_t:lnk_file read;
  113. <br>allow httpd_sys_script_t sysctl_kernel_t:file read;
  114. <br>allow httpd_sys_script_t unconfined_t:unix_stream_socket connectto;
  115. <p><li><h4>session timeouts</h4>
  116. If you get frequent timeouts or can't even log in, synchronize
  117. the clocks between the server and workstation.
  118. <p><li><h4>lineitems not printing</h4>
  119. Templates designed on a UNIX platform don't work on a DOS platform.
  120. To make them work load the template either with the builtin template editor
  121. or a text editor and save. Templates designed on a Windows platform have the
  122. same problem and won't work on a UNIX platform. Once you strip the ^M's
  123. the'll work just fine.
  124. </p><p>
  125. Note too that most Linux and UNIX installations come with two utilities for making these
  126. conversions: unix2dos and dos2unix. Windows users can obtain these utilities as part of
  127. <a href="http://www.cygwin.com">Cygwin</a>.</p>
  128. <p><li><h4>UTF-8 character encoding</h4>
  129. Most of the translations are in ISO format. To convert the translations
  130. change directory to locale/cc and convert the files with iconv to UTF-8.
  131. You should also convert the COAs too and make sure you select UTF-8
  132. encoding when you set up a new dataset.
  133. <p><li><h4>characterset problems</h4>
  134. If you have problems displaying the correct characterset try adding
  135. <pre>
  136. AddDefaultCharset On</pre>
  137. in your <tt>httpd.conf</tt> file.
  138. <p><li><h4>About installation</h4>
  139. The easiest is to use the setup.pl script as root.
  140. You don't need to know very much about your system, just login as root,
  141. run 'perl setup.pl' and follow the prompts.
  142. <p>setup.pl does not check for missing software packages and it is your
  143. responsibility to make sure you have the required software
  144. installed either from source or from a package.
  145. <p>Requirements are clearly indicated in the <tt>README</tt> file and
  146. on the download page.
  147. <p><li><h4>cannot create function</h4>
  148. <ol>
  149. <li>either run <tt>createlang plpgsql</tt> to install the plpgsql
  150. language handler or install yourself. For more information how to do
  151. that, visit <a href=http://www.postgresql.org/docs/>PostgreSQL</a> and
  152. read the interactive documentation for procedural languages.
  153. <li>load admin.pl
  154. <li>unlock the system
  155. <li>login
  156. </ol>
  157. <p><li><h4>The requested URL /ledger-smb/admin.pl was not found</h4>
  158. Your webserver doesn't know where to find the script. Most commonly this
  159. results when distributions hide webserver configuration files in unexpected
  160. locations so that <tt>setup.pl</tt> wasn't able to configure the location for
  161. you. Find out which file (<tt>httpd.conf</tt>, <tt>httpdcommon.conf</tt>, ...)
  162. controls your webserver configuration and add
  163. <pre>
  164. # LedgerSMB
  165. Include /etc/httpd/ledger-smb-httpd.conf</pre>
  166. Create a file 'ledger-smb-httpd.conf' in /etc/httpd and copy the next part
  167. into the file.
  168. <pre>
  169. AddHandler cgi-script .pl
  170. AddDefaultCharset On
  171. Alias /ledger-smb /var/www/ledger-smb/
  172. &lt;Directory /var/www/ledger-smb&gt;
  173. Options ExecCGI Includes FollowSymlinks
  174. &lt;/Directory&gt;
  175. &lt;Directory /var/www/ledger-smb/users&gt;
  176. Order Deny,Allow
  177. Deny from All
  178. &lt;/Directory&gt;</pre>
  179. replace '/etc/httpd' and '/var/www' with the appropriate directories.
  180. <p><li><h4>users/members : Permission denied</h4>
  181. Your webserver must have write access to the users directory.
  182. If your server runs as user/group 'apache:apache' then set the
  183. users directory to owner/group apache:apache.
  184. <pre>
  185. # chown -R apache:apache users</pre>
  186. <p><li><h4>Dataset newer than version</h4>
  187. You are trying to use an older version with a dataset which was
  188. created with a newer version.
  189. <p><li><h4>PDF option not working</h4>
  190. Check if you have latex and pdflatex installed.
  191. <p><li><h4>Apache 2.0 "error 500"</h4>
  192. Some of the early versions of Apache 2.0 (&lt; patchlevel 44) had a rewrite engine
  193. which decoded escaped strings. This created a lot of problems and I worked
  194. around it by escaping strings twice.
  195. If you get a server 500 error 'filename too long' or if collapsed menus
  196. don't expand you may have to adjusted the following code in
  197. SL/Form.pm and change the number (44) on line 84.
  198. <pre>
  199. # for Apache 2 we escape strings twice
  200. if (($ENV{SERVER_SIGNATURE} =~ /Apache\/2\.(\d+)\.(\d+)/) && !$beenthere) {
  201. $str = $self->escape($str, 1) if $2 < 44;
  202. }</pre>
  203. <p><li><h4>IDENT Authentication failed for user "sledger-smb"</h4>
  204. Edit pg_hba.conf and change authentication to
  205. <pre>
  206. local all all MD5</pre>
  207. The file is in the 'data' directory of your postgresql installation.
  208. This is different with every distribution so look for it.
  209. <pre>
  210. # find / -name 'pg_hba.conf'</pre>
  211. <p>Some people can't read and seem to think 'localhost' is just some
  212. fancy word for a local machine.
  213. 'localhost' is a host like any other host on a network.
  214. A 'local' entry in pg_hba.conf will allow socket connections ONLY and
  215. not allow a host connection. If you then try to connect to 'localhost',
  216. PostgreSQL will come back with an authentication error.
  217. <p>So, if the database resides on the same server as the web server,
  218. forget you ever heard there is such a thing as 'localhost' and leave
  219. the Host portion blank.
  220. <p><b>WARNING!</b> DO NOT just put a 'host all all trust' in
  221. pg_hba.conf unless you know what you are doing; that can introduce a
  222. pretty huge security hole.
  223. <p><li><h4>DBD-Pg for Mandrake 9.0</h4>
  224. Mandrake did not package a compiled DBD-Pg package again, so install DBD-Pg
  225. from the source package.
  226. Install perl-DBD-Pg-1.01-4mdk.i586.rpm from the 'contrib' area.
  227. (Mandrake / 9.0 / contrib / RPMS)
  228. <p><li><h4>LaTeX error</h4>
  229. If for some reason LaTeX produces an error message check for strange
  230. characters in your account description and parts description
  231. and use \usepackage[latin1]{inputenc} in the preamble.
  232. <p><li><h4>LaTeX templates</h4>
  233. If you don't want to edit tex code by hand,
  234. you could use Lyx, Abiword, or any WYSIWYG editor capable of exporting
  235. latex code.
  236. To do that you must change the tokens for the variables <% and %> to something
  237. like << and >>. % is the comment character in tex. There is also a
  238. pagebreak block which must be commented out.
  239. When you are done with the changes
  240. replace << and >> with <% and %> and uncomment the pagebreak block.
  241. <p>LaTeX is somewhat complex to learn, initially, but offers a much
  242. superior environment to produce professional-looking forms in
  243. postscript and PDF format.
  244. <p><li><h4>W3M</h4>
  245. pass terminal=mozilla when you start w3m
  246. <pre>
  247. $ w3m -F http://localhost/ledger-smb/login.pl?terminal=mozilla</pre>
  248. To use without frames
  249. <pre>
  250. $ w3m http://localhost/ledger-smb/login.pl?terminal=lynx</pre>
  251. <p><li><h4>PDF option disappeared</h4>
  252. Edit ledger-smb.conf and set $latex = 1;
  253. <br>ledger-smb.conf is perl code, check if it compiles, if it does not,
  254. the internal defaults are used which turn off $latex, hence no PDF option.
  255. <p><li><h4>Installation on Windows (WIN32)</h4>
  256. <ul>
  257. <li>install Apache, perl,
  258. <a href=http://techdocs.postgresql.org/guides/InstallingOnWindows>Postgres</a>
  259. or Oracle, DBI and the appropriate DBD
  260. module
  261. <br>if you can't compile DBD-Pg here is a precompiled
  262. <a href=http://http://pgfoundry.org/projects/dbdpgppm/>DBD-Pg module</a>
  263. <li>download the latest version of <a
  264. href="http://www.ledgersmb.org/download/">LedgerSMB</a>
  265. <li>extract the files to c:\apache\ledger-smb
  266. <li>run 'perl shebang' to change the first line of the scripts. If perl
  267. is not in c:\perl\bin' change '#!c:\\perl\\bin\\perl' to the location where
  268. your perl binary is.
  269. <li>edit c:\apache\conf\httpd.conf and add
  270. <pre>
  271. Alias /ledger-smb "c:/apache/ledger-smb/"
  272. &lt;Directory "c:/apache/ledger-smb"&gt;
  273. AllowOverride All
  274. AddHandler cgi-script .pl
  275. AddDefaultCharset On
  276. Options +ExecCGI
  277. Order Allow,Deny
  278. Allow from All
  279. &lt;/Directory&gt;
  280. &lt;Directory "c:/apache/ledger-smb/users"&gt;
  281. Order Deny,Allow
  282. Deny from All
  283. &lt;/Directory&gt;
  284. </pre>
  285. <li>start Apache
  286. <li>start Postgres|Oracle|DB2
  287. <li>connect to http://localhost/ledger-smb/admin.pl and set up users
  288. and datasets
  289. <li>connect to http://localhost/ledger-smb/login.pl and login
  290. </ul>
  291. <p><li><h4>What do I enter for the language</h4>
  292. If you use English, nothing, if you want to use a foreign language for
  293. the login screen and admin stuff enter the language code, this is the
  294. directory in the locale directory.
  295. <p><li><h4>printing to a printer</h4>
  296. Printers are defined in ledger-smb.conf
  297. <pre>
  298. %printer = ( 'Default' => 'lpr', 'Color' => 'lpr -PEpson' );</pre>
  299. Check in your /etc/printcap file for the names of available printers.
  300. <p>If you have LaTeX installed set
  301. <pre>
  302. $latex = 1</pre> in ledger-smb.conf
  303. <p>To send the document to the printer check the "Postscript" or "PDF" format,
  304. enter the number of copies and click on the "Print" button.
  305. <p>The printer you enter in your preferences is the default printer.
  306. You can choose any other available printer. This makes it possible
  307. to print from anywhere on the network to any printer.
  308. <p>Note: html format is for screen preview. Use the "Print" option from your
  309. browser to print to a printer.
  310. <p><li><h4>Using samba to send printjobs to a printer attached to a Windows XP workstation</h4>
  311. The next part applies to roll your own print filters only. If you use CUPS or
  312. LPRng your milage may vary but you can still use this as a guide how it works.
  313. I use the printer 'Epson' as an example which is
  314. attached to a XP workstation called Raven.
  315. <pre>
  316. /etc/printcap entry on the server which runs lpd
  317. epson:Epson\
  318. :sh:\
  319. :lp=/dev/null:\
  320. :sd=/var/spool/output/epson:\
  321. :if=/usr/libexec/lpr/epson/prnfilter:\
  322. # end of entry in /etc/printcap
  323. # prnfilter shell script
  324. #!/bin/sh
  325. # Filter for Epson Stylus
  326. PATH="$PATH:/usr/local/bin"
  327. #read first_line
  328. read tmp
  329. first_line=`echo $tmp | cut -b1-2 | sed -n '1p'`
  330. first_chr=`expr "$first_line" : '\(.\)'`
  331. first_two=`expr "$first_line" : '\(..\)'`
  332. rewindstdin
  333. if [ "$first_two" = "%!" ]; then # Postscript file
  334. gs @st640p.upp -dSAFER -dNOPAUSE -q -sOutputFile=/tmp/$$ -
  335. else
  336. # text file
  337. cat &gt; /tmp/$$
  338. echo -n "^L" &gt;&gt; /tmp/$$
  339. smbclient '\\Raven\Epson' "" -c 'printmode text'
  340. fi
  341. smbclient '\\Raven\Epson' "" -P -c "print /tmp/$$"
  342. rm /tmp/$$
  343. # EOF
  344. rewindstdin is a small program to rewind the filehandle for STDIN
  345. save the next part up to EOF to a file rewindstdin.c and compile
  346. #include &lt;sys/types.h&gt;
  347. #include &lt;unistd.h&gt;
  348. extern int errno;
  349. main()
  350. {
  351. if( lseek(0,0,0) == 0 ){
  352. errno = 0;
  353. }
  354. return( errno );
  355. }
  356. # EOF
  357. compile to an executable
  358. gcc -o /usr/local/bin/rewindstdin rewindstdin.c
  359. </pre>
  360. <p><li><h4>beginning balances</h4>
  361. Add a GL Journal entry and enter the beginning balance for your accounts.
  362. Beginning balances are the balances from your last balance sheet. If you also
  363. add open invoices to account for COGS for inventory, add the invoices
  364. and make the appropriate adjustments.
  365. <p><li><h4>establish a beginning inventory</h4>
  366. add the parts with a vendor invoice. Use the <b>real cost</b> for the items,
  367. not zero. If you use zero cost then the cost of goods will be zero when you
  368. sell the item.
  369. <p><li><h4>Assemblies</h4>
  370. Assemblies are manufactured goods assembled from parts, services and
  371. assemblies. Because you do not buy assemblies you 'stock assemblies' by
  372. adding assembled units to your inventory. The quantity for individual parts
  373. is reduced and the quantity for the assembly increased. To disassemble an
  374. assembly you simply return the parts to inventory by entering a negative
  375. quantity for the number of assemblies to stock.
  376. <p><li><h4>DBD-Pg not installed</h4>
  377. Most modern distributions now package DBD-Pg. If it is
  378. not packaged follow this recipe to get it working.
  379. <ul>
  380. <li>check if you have the header files for PostgreSQL
  381. <br>$ find / -name 'libpq-fe.h'
  382. <br>if nothing shows up install the development package for PostgreSQL
  383. <li>download and untar DBD-Pg
  384. <li>set the environment variables POSTGRES_LIB and POSTGRES_INCLUDE
  385. <li>cd to DBD-Pg directory
  386. <br>as ordinary user
  387. <br>$ perl Makefile.PL
  388. <br>$ make
  389. <br>$ make test
  390. <br>if all went well su to root
  391. <br># make install
  392. <li>remove DBD-Pg
  393. </ul>
  394. <p><li><h4>login.pl has compilation error</h4>
  395. This could be because of a missing configuration file in the users directory
  396. <p>check the permission for the users directory. The directory must be
  397. set writeable for the webserver. If your webserver runs ias user/group
  398. nobody.nogroup set the directory to
  399. <pre>
  400. drwx--x--x 2 nobody nogroup 1024 May 26 16:49 users
  401. or
  402. drwxrwx--x 2 johndoe nogroup 1024 May 26 16:49 users</pre>
  403. <p><li><h4>script not executing, shows in browser instead</h4>
  404. Add
  405. <pre>
  406. AddHandler cgi-script .pl</pre>
  407. in your httpd.conf file.
  408. <p><li><h4>permission denied</h4>
  409. Check if your web server has write permission to write to the following
  410. files and directories:
  411. <pre>
  412. users/
  413. templates/
  414. users/members
  415. # chown nobody:nogroup users templates users/members
  416. </pre>
  417. <p><li><h4>permission denied to access tables</h4>
  418. The user you entered in the "Database section" must be a valid
  419. database user who has rights to access the tables.
  420. <p>If the tables are owned by 'joe' and you enter 'mary' as the dba
  421. you might run into this problem if mary doesn't have the rights to
  422. access tables owned by joe.
  423. <p><li><h4>html and graphics files don't show up on screen</h4>
  424. Enable Includes and FollowSymlinks Options in your httpd.conf file
  425. <pre>
  426. &lt;Directory /usr/local/ledger-smb&gt;
  427. Options ExecCGI Includes FollowSymlinks
  428. &lt;/Directory&gt;
  429. </pre>
  430. <p><li><h4>switch display to a foreign language</h4>
  431. Load your preferences and select the language.
  432. <br>Language selection is in accordance to
  433. <a href=http://www.unece.org/cefact/locode/service/main.htm>
  434. ISO 3166-1</a> standards.
  435. <p><li><h4>Text shows in English when I use a foreign language</h4>
  436. This is because the corresponding hash entry is missing.
  437. Add the missing text in the locale/cc/all or locale/cc/missing
  438. file and run 'perl locales.pl' from the command line to rebuild
  439. the individual files.
  440. <br>cc refers to the country code.
  441. <p><li><h4>switch to a foreign language for the login and admin screen</h4>
  442. Edit ledger-smb.conf and enter the code for the $language variable
  443. <pre>
  444. $language = "de";</pre>
  445. <p>This is a global change and applies to all logins, individual settings
  446. may be changed by setting the language in your Preferences.
  447. </ul>
  448. <p>
  449. <hr>
  450. <a name=security>
  451. <h1>LedgerSMB security</h1>
  452. </a>
  453. <ul>
  454. <li>The security features built into LedgerSMB provide encrypted passwords
  455. and access control which makes it fairly safe out of the box to run even in
  456. front of a firewall.
  457. Some precautions which are out of our control must be taken though.
  458. It matters where you install SL and how you configure your web server and
  459. SQL server.
  460. <pre>
  461. Typical setups:
  462. /usr/local/vh/www <- DocumentRoot for virtual host
  463. /usr/local/vh/ledger-smb <- Alias for ledger-smb
  464. /usr/local/vh/users <- users directory out of reach
  465. <hr width=60% align=left>
  466. /usr/local/vh/www <- DocumentRoot for virtual host
  467. /usr/local/vh/www/ledger-smb <- Alias for ledger-smb
  468. /usr/local/vh/www/ledger-smb/users <- users configuration files and tmp space
  469. &lt;Directory /usr/local/vh/www/ledger-smb/users&gt; <- disable webserver access
  470. Order Deny,Allow for users directory
  471. Deny from All
  472. &lt;/Directory&gt;
  473. </pre>
  474. The location for the users directory can be specified in ledger-smb.conf
  475. <p><li>Set permission for the users and templates directory to 711
  476. <p><li>If you do not want anyone to change the templates with the built-in
  477. editor set the files in templates/directory/ to read only or disable
  478. the menu item to edit the templates.
  479. <p><li>You can set up a read-only environment if you disable the menu items
  480. to add data. i.e 'Add Transaction' if unchecked you will not be able to add
  481. a transaction or repost a transaction. You may look at it but nothing else.
  482. <p><li>There are various settings for audit control and you may disable
  483. reposting entirely or up to a certain date. And with the audit trail enabled
  484. you can keep tab of who is doing what.
  485. <p><li>For PostgreSQL you may also set who has access to the server in the file
  486. pg_hba.conf
  487. <br>Authentication crypt does not work because not all SQL servers
  488. accept encrypted passwords.
  489. <p><li>in addition you can secure the tables from unauthorized access by
  490. setting up a different database user and GRANT rights. For instance,
  491. users without DELETE rights will still be able to use the program, change
  492. customers and vendors, add transactions but will not be able to delete or
  493. repost transactions.
  494. <br>To lock all the tables to create a RO system GRANT SELECT rights only.
  495. <p><li>Other security options include a secure shell, your webserver's
  496. authentication system, SSL, encrypted tunnels, ...
  497. </ul>
  498. </BODY>
  499. </HTML>