Menu
▾
▴
sql-ledger-users
|
From: Roderick A. A. <raa...@ti...> - 2001-08-21 20:54:31
|
Damn! I'm havin a heck of a time. I upgraded my system to RHL 7.1,
installed PostgreSQL 7.1.3, installed (upgraded) to SQL-Ledger 1.6 and
now can't get it to work. I'm trying to get to the admin page and keep
getting the message in the Subject line. I know the PostgreSQL driver
is install and perl can find it because
perl -e 'use DBI::Pg; print join('\n', DBI->available_drivers())';
shows Pg.
The Apache log (error_log) shows
Compilation failed in require at /home/httpd/sql-ledger/admin.pl line 89
Any ideas?
TIA,
Rod
--
|
|
From: Dieter S. <dsi...@sq...> - 2001-08-21 21:28:54
|
try this perl -e 'use DBI; print join "\n", DBI->available_drivers'; That should list all the available drivers. Dieter Simader http://www.sql-ledger.org (780) 472-8161 DWS Systems Inc. Accounting Software Fax: 478-5281 =========== On a clear disk you can seek forever =========== On Tue, 21 Aug 2001, Roderick A. Anderson wrote: > Damn! I'm havin a heck of a time. I upgraded my system to RHL 7.1, > installed PostgreSQL 7.1.3, installed (upgraded) to SQL-Ledger 1.6 and > now can't get it to work. I'm trying to get to the admin page and keep > getting the message in the Subject line. I know the PostgreSQL driver > is install and perl can find it because > > perl -e 'use DBI::Pg; print join('\n', DBI->available_drivers())'; > > shows Pg. > > The Apache log (error_log) shows > > Compilation failed in require at /home/httpd/sql-ledger/admin.pl line 89 > > Any ideas? > > > TIA, > Rod > |
|
From: Roderick A. A. <raa...@ti...> - 2001-08-22 12:26:01
|
On Tue, 21 Aug 2001, Dieter Simader wrote: > try this > > perl -e 'use DBI; print join "\n", DBI->available_drivers'; > > That should list all the available drivers. This is what puzzles me. $ perl -e 'use DBI; print join "\n", DBI->available_drivers' ADO ExampleP Multiplex Pg Proxy By default perl (well the DBI bundle anyway) includes all the above except Pg. Rod Roark mentioned re-building DBD-Pg. The new releases of the PostgreSQL RPMs come with perl (and the DBD driver) ready to run. but I did build PostgreSQL from the RPM source before installing. I'm working on a clean install of RHL7.1 plus errata to determine if the problem is the upgrade process. Thanks, Rod -- |
|
From: <ro...@su...> - 2001-08-22 13:30:22
|
> Rod Roark mentioned re-building DBD-Pg. The new releases of the > PostgreSQL RPMs come with perl (and the DBD driver) ready to run. but I > did build PostgreSQL from the RPM source before installing. Let me try again. If you upgrade Postgres, then you *must* also compile DBD-Pg. This includes a "make test" that you should run and actually look at its results. You can get the latest DBD-Pg from: http://www.perl.com/CPAN-local/modules/by-module/DBD/. Check its README file for troubleshooting tips. Cheers, -- Rod |
|
From: Roderick A. A. <raa...@ti...> - 2001-08-22 16:55:54
|
On Wed, 22 Aug 2001, [iso-8859-1] Rod Roark wrote: > > Rod Roark mentioned re-building DBD-Pg. The new releases of the > > PostgreSQL RPMs come with perl (and the DBD driver) ready to run. but I > > did build PostgreSQL from the RPM source before installing. > > Let me try again. If you upgrade Postgres, then you > *must* also compile DBD-Pg. This includes a "make test" > that you should run and actually look at its results. > I think I found the problem. The version of DBD-Pg I had installed was for perl 5.005. The version of perl installed was 5.6.0 (i386), the version of PostgreSQL was 7.1 (i686). Perl wasn't finding the module because the i686-linux directories weren't in perl's search path. I'm down loading the perl RPM and will compile perl for the i686 platform and see how that works with the PostgreSQL i686 DBD-Pg driver. > You can get the latest DBD-Pg from: > http://www.perl.com/CPAN-local/modules/by-module/DBD/. > Check its README file for troubleshooting tips. Actually the 'almost' latest (1.0 verses 1.01) is included in the PostgreSQL distribution. Rod -- |
|
From: Jeff K. <jt...@ad...> - 2001-08-23 14:04:29
|
I realize this is a pretty complicated feature, but is the basic structure of SQL-ledger conducive to someday having the capability to take transactions in more than one currency? This is a complicated issue, I don't know whether standard practice for an international company with remote offices is to convert everything to the local currency for each transaction, or to have exchange-rate transactions to get things back to the home currency at certain points of the fiscal year, or during advantageous exchange rates. |
|
From: Federico S. I. <ji...@le...> - 2001-08-23 15:36:15
|
On Thu, 23 Aug 2001 at 10:04, Jeff Kowalczyk wrote: > This is a complicated issue, I don't know whether standard practice > for an international company with remote offices is to convert > everything to the local currency for each transaction, or to have > exchange-rate transactions to get things back to the home currency at > certain points of the fiscal year, or during advantageous exchange > rates. I just thought I'd raise a concern here. I'm from the Philippines and here, believe me, the foreign exchange rates are more volatile than the rise and fall of the tides. That would be something quite difficult to deal with, although I don't think first world countries experience such volatility. --> Jijo -- Federico Sevilla III :: ji...@le... Network Administrator :: The Leather Collection, Inc. GnuPG Key: <http://jijo.leathercollection.ph/jijo.gpg> |
|
From: Jeff K. <jt...@ad...> - 2001-08-23 16:18:20
|
[Jijo] I just thought I'd raise a concern here. I'm from the Philippines and here, believe me, the foreign exchange rates are more volatile than the rise and fall of the tides. That would be something quite difficult to deal with, although I don't think first world countries experience such volatility. [jeff] If a US company did business there, purchased inventory and sold goods in the local currency, but reported back to a US concern, would everything be accounted for in Phillipine Dollars or US dollars? |
|
From: John C. N. y L. <nj...@nt...> - 2001-08-24 00:44:10
|
Jeff Kowalczyk wrote:
>
> [Jijo] I just thought I'd raise a concern here. I'm from the Philippines
> and here, believe me, the foreign exchange rates are more volatile than
> the rise and fall of the tides. That would be something quite difficult
> to deal with, although I don't think first world countries experience
> such volatility.
>
> [jeff] If a US company did business there, purchased inventory and sold
> goods in the local currency, but reported back to a US concern, would
> everything be accounted for in Phillipine Dollars or US dollars?
I'm also here in the Philippines, but AFAIK, we don't have Philippine
Dollars, we do have Philippine Peso, however...;-)
And the FOREX Rates are quite volatile, last week it was at around PHP53
to a $, now it's PHP51, perhaps next week it'll be PHP52...;-)
AFAIK, if you haven't converted your money from the local currency, to
that of your company's mother currency (i.e. U.S. dollars), then you
should base it on the current FOREX rates. Once you have converted the
local currency, however, to that of your desired currency, then you can
start using that figure for the future...;-)
Perhaps you can relate it to the stock market, on having paper
loss/profit and real loss/profit...;-)
At least, that's my 2 centavos worth...;-)
Cheers,
John Clark
--
/) John Clark Naldoza y Lopez (\
/ ) Software Design Engineer III ( \
_( (_ _ Web-Application Development _) )_
(((\ \> /_> Cable Modem Network Management System <_\ </ /)))
(\\\\ \_/ / NEC Telecom Software Phils., Inc. \ \_/ ////)
\ / \ /
\ _/ phone: (+63 32) 233-9142 loc. 3113 \_ /
/ / cellphone: (+63 919) 399-4742 \ \
/ / email: nj...@nt... \ \
"Intelligence is the ability to avoid doing work, yet getting the work
done"
--Linus Torvalds
|
|
From: Matt B. <ma...@li...> - 2001-09-07 19:46:13
|
Since upgrading from 1.4.7 to 1.6.2, we can no longer process receipts. The proximate cause seems to be a delete on acc_trans with an empty account number. Any info on this? Matt Matt Benjamin The Linux Box 206 South Fifth Ave. Suite 150 Ann Arbor, MI 48104 tel. 734-761-4689 fax. 734-769-8938 pgr. 734-431-0118 |
|
From: James C. <jam...@ya...> - 2001-09-08 03:07:54
|
I just installed the software today on Linux 7.1 It all went very well, in fact I was suprised how well it went. However... when I try to login from sql-ledger/login.pl I get the following error ========================================= Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. -------------------------------------------------------------------------------- Apache/1.3.19 Server at localhost.localdomain Port 80 ======================================== I looked in the server error log and it says: computation failed in require at /var/www/sql-ledger/login.pl line 76. can't locate /test.conf at SL/user.pm line 115 compilation failed at /var/www/sql-ledger/login.pl line 76. premature end of script headers: /var/www/sql-ledger/login.pl I think I configured something wrong, but can't find the problem. Anyone have any ideas? or had any problems with redhat 7.1? The only difference I am aware of regarding this issue is the location of /www/ from previous versions of Red Hat. Thanks James Cluff jam...@ya... --- Matt Benjamin <ma...@li...> wrote: > > Since upgrading from 1.4.7 to 1.6.2, we can no > longer process receipts. > The proximate cause seems to be a delete on > acc_trans with an empty > account number. > > Any info on this? > > Matt > > > Matt Benjamin > > The Linux Box > 206 South Fifth Ave. Suite 150 > Ann Arbor, MI 48104 > > tel. 734-761-4689 > fax. 734-769-8938 > pgr. 734-431-0118 > > > __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com |
|
From: Roderick A. A. <raa...@ti...> - 2001-09-08 03:27:40
|
On Fri, 7 Sep 2001, James Cluff wrote:
> computation failed in require at
> /var/www/sql-ledger/login.pl line 76.
> can't locate /test.conf at SL/user.pm line 115
Did you use the admin.pl script to create the 'test' user and/or
database?
I've got a similar error except it was "can't locate /.conf ...".
I'm thinking there may be some form artifacts laying around between
calls to the script that cause the /.conf error so they may also cause
some other non- user/database names to appear.
Cheers,
Rod
--
A small clue and no money
will get you further than
lots of money and no clue.
|
|
From: Dieter S. <dsi...@sq...> - 2001-09-08 17:45:53
|
the webserver could not write to the users directory. set the directory owner to the one your server runs as (nobody.nogroup) Dieter Simader http://www.sql-ledger.org (780) 472-8161 DWS Systems Inc. Accounting Software Fax: 478-5281 =========== On a clear disk you can seek forever =========== On Fri, 7 Sep 2001, James Cluff wrote: > I just installed the software today on Linux 7.1 It > all went very well, in fact I was suprised how well it > went. > > However... > > when I try to login from sql-ledger/login.pl > I get the following error > ========================================= > > Internal Server Error > The server encountered an internal error or > misconfiguration and was unable to complete your > request. > Please contact the server administrator, > root@localhost and inform them of the time the error > occurred, and anything you might have done that may > have caused the error. > > More information about this error may be available in > the server error log. > > > > -------------------------------------------------------------------------------- > > Apache/1.3.19 Server at localhost.localdomain Port 80 > > ======================================== > > > I looked in the server error log and it says: > > computation failed in require at > /var/www/sql-ledger/login.pl line 76. > can't locate /test.conf at SL/user.pm line 115 > > compilation failed at /var/www/sql-ledger/login.pl > line 76. > premature end of script headers: > /var/www/sql-ledger/login.pl > > I think I configured something wrong, but can't find > the problem. Anyone have any ideas? or had any > problems with redhat 7.1? The only difference I am > aware of regarding this issue is the location of /www/ > from previous versions of Red Hat. > > Thanks > James Cluff > jam...@ya... > |
|
From: James C. <jam...@ya...> - 2001-09-08 19:52:42
|
Dieter, I am not sure exactly what you mean. I read through the httpd.conf and a linux manual. I am relatively new to linux. I don't want to trouble you, but could you be more explicit? Thank you James --- Dieter Simader <dsi...@sq...> wrote: > the webserver could not write to the users > directory. > > set the directory owner to the one your server runs > as (nobody.nogroup) > > > Dieter Simader http://www.sql-ledger.org (780) > 472-8161 > DWS Systems Inc. Accounting Software Fax: > 478-5281 > =========== On a clear disk you can seek forever > =========== > > On Fri, 7 Sep 2001, James Cluff wrote: > > > I just installed the software today on Linux 7.1 > It > > all went very well, in fact I was suprised how > well it > > went. > > > > However... > > > > when I try to login from sql-ledger/login.pl > > I get the following error > > ========================================= > > > > Internal Server Error > > The server encountered an internal error or > > misconfiguration and was unable to complete your > > request. > > Please contact the server administrator, > > root@localhost and inform them of the time the > error > > occurred, and anything you might have done that > may > > have caused the error. > > > > More information about this error may be available > in > > the server error log. > > > > > > > > > -------------------------------------------------------------------------------- > > > > Apache/1.3.19 Server at localhost.localdomain Port > 80 > > > > ======================================== > > > > > > I looked in the server error log and it says: > > > > computation failed in require at > > /var/www/sql-ledger/login.pl line 76. > > can't locate /test.conf at SL/user.pm line 115 > > > > compilation failed at /var/www/sql-ledger/login.pl > > line 76. > > premature end of script headers: > > /var/www/sql-ledger/login.pl > > > > I think I configured something wrong, but can't > find > > the problem. Anyone have any ideas? or had any > > problems with redhat 7.1? The only difference I > am > > aware of regarding this issue is the location of > /www/ > > from previous versions of Red Hat. > > > > Thanks > > James Cluff > > jam...@ya... > > > > __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com |
|
From: Steve D. <sd...@sw...> - 2001-08-24 03:53:11
|
Jeff Kowalczyk wrote: > [Jijo] I just thought I'd raise a concern here. I'm from the Philippines > and here, believe me, the foreign exchange rates are more volatile than > the rise and fall of the tides. That would be something quite difficult > to deal with, although I don't think first world countries experience > such volatility. > > [jeff] If a US company did business there, purchased inventory and sold > goods in the local currency, but reported back to a US concern, would > everything be accounted for in Phillipine Dollars or US dollars? The Phillipine based company would keep their books in Phillipine peso's. Then the foreign currency financial statements are translated to US dollars before the parent reports results. Translation rules are very specific, with some items (i.e. monetary assets like cash and receivables) translated at current rates, and historical cost based assets and liabilities at historical rates (like a building). Revenues and expenses are translated at the rate on the transaction date, or an average for the period. The parent would make a journal entry to reflect the net translation effect. There isn't really a need to handle multiple currencies, because each operation would and should keep their books entirely in the local currency. |
|
From: Jeff K. <jt...@ad...> - 2001-08-23 14:55:32
|
I was curious what 'traditional chinese' would look like. Of course, I'm using the US-english version of Windows and Internet Explorer. I added the 'languages...' listed below to internet options. English (United States)[en-us] Chinese [zh] Chinese (Tiawan) [zh-tw] And created a SQL-Ledger user that has the chinese language preference. I left charset blank. I also left stylesheet blank to avoid font problems. With this user, I only see the font-glyphs that are in the same character-code, not the chinese characters shown in the full chinese sample on the sql-ledger website. Is what I'm trying to do possible? Does it have to do with the charset, or do I need some special chinese font? |
|
From: <ro...@su...> - 2001-08-21 23:13:58
|
Did you rebuild DBD-pg? -- Rod http://www.sunsetsystems.com/ > Damn! I'm havin a heck of a time. I upgraded my system to RHL 7.1, > installed PostgreSQL 7.1.3, installed (upgraded) to SQL-Ledger 1.6 and > now can't get it to work. I'm trying to get to the admin page and keep > getting the message in the Subject line. I know the PostgreSQL driver > is install and perl can find it because > > perl -e 'use DBI::Pg; print join('\n', DBI->available_drivers())'; > > shows Pg. > > The Apache log (error_log) shows > > Compilation failed in require at /home/httpd/sql-ledger/admin.pl line > 89 > > Any ideas? > > > TIA, > Rod > -- |
Thanks for helping keep SourceForge clean.
X