Última discussão há 4 d

Fórum FrontAccounting forum

frontaccounting.com/punbb

Fórum PunBB em inglês. 11 seções acompanhadas: Reporting, Installation, Announcements, Banking and General Ledger, Banking and General Ledger, Setup, Accounts Receivable, Accounts Payable, Items and Inventory, Manufacturing e Dimensions.

Discussões por dia
0
Discussões coletadas
115
Mensagens por dia
9
Seções
11
Fontes acompanhadas
15
Motor
PunBB

Últimas discussões

Coletadas a cada 4 horas do feed público do fórum. Reproduzimos apenas o título, o link e o começo da mensagem; cada link leva à fonte.

Problem with Transaction References not looking at prefix...

it appears that the Transaction References do not look at the prefix when determining uniqueness. I have 2 Supplier Transaction References set up. 1 with no prefix (generic payments) and 1 with a prefix (checking account and check number as a reference) When entering a Supplier Payment, only the reference number is check for uniqueness, preventing references with the same number but different prefixes from being accepted. It seems that the Supplier Payment form will return the Reference List (ref_list) index but not the prefix value. Is there an easy way to allow duplicate reference numbers with different prefixes? Thanks

Problem with Transaction References not looking at prefix...

it appears that the Transaction References do not look at the prefix when determining uniqueness. I have 2 Supplier Transaction References set up. 1 with no prefix (generic payments) and 1 with a prefix (checking account and check number as a reference) When entering a Supplier Payment, only the reference number is check for uniqueness, preventing references with the same number but different prefixes from being accepted. It seems that the Supplier Payment form will return the Reference List (ref_list) index but not the prefix value. Is there an easy way to allow duplicate reference numbers with different prefixes? Thanks

Problem with Transaction References not looking at prefix...

it appears that the Transaction References do not look at the prefix when determining uniqueness. I have 2 Supplier Transaction References set up. 1 with no prefix (generic payments) and 1 with a prefix (checking account and check number as a reference) When entering a Supplier Payment, only the reference number is check for uniqueness, preventing references with the same number but different prefixes from being accepted. It seems that the Supplier Payment form will return the Reference List (ref_list) index but not the prefix value. Is there an easy way to allow duplicate reference numbers with different prefixes? Thanks

Edit Invoice using posted Wiki

I tried to to change an existing Invoice using the procedure posted in the Wiki and the results created parts of the new Invoice with redundant invoice numbers instead of creating unique new numbers. I could not find out why. This is the first time I've tried to change an invoice with this level of software (2.4.19 Default Theme, Church Chart of Accounts). I'm listing all the changes in the DB when I changed one invoice. If any one can help me or even verify that I should see different results and why, then I'll know I did something wrong. Edit Invoice using posted Wiki Results posted below. 0_audit_trail ('32595', '30', '6472', '1', '2026-05-06 07:17:23', NULL, '8', '2026-04-26', '0'), (Original) ('32596', '13', '6473', '1', '2026-05-06 07:17:23', NULL, '8', '2026-04-26', '0'), (Original) ('32597', '10', '6473', '1', '2026-05-06 07:17:23', NULL, '8', '2026-04-26', '0'), (Original) ********************************************************************************************* ('32595', '30', '6472', '1', '2026-08-15 19:30:10', NULL, '8', '2026-04-26', NULL), (Changed) ('32596', '13', '6473', '1', '2026-08-15 19:28:04', NULL, '8', '2026-04-26', NULL), (Changed) ('32597', '10', '6473', '1', '2026-08-15 19:28:04', NULL, '8', '2026-04-26', NULL), (Changed) ********************************************************************************************* ('34130', '13', '6473', '1', '2026-08-15 19:28:04', 'Voided.', '8', '2026-04-26', '0'), (New Addition) ('34131', '10', '6473', '1', '20

Edit Invoice using posted Wiki

I tried to to change an existing Invoice using the procedure posted in the Wiki and the results created parts of the new Invoice with redundant invoice numbers instead of creating unique new numbers. I could not find out why. This is the first time I've tried to change an invoice with this level of software (2.4.19 Default Theme, Church Chart of Accounts). I'm listing all the changes in the DB when I changed one invoice. If any one can help me or even verify that I should see different results and why, then I'll know I did something wrong. Edit Invoice using posted Wiki Results posted below. 0_audit_trail ('32595', '30', '6472', '1', '2026-05-06 07:17:23', NULL, '8', '2026-04-26', '0'), (Original) ('32596', '13', '6473', '1', '2026-05-06 07:17:23', NULL, '8', '2026-04-26', '0'), (Original) ('32597', '10', '6473', '1', '2026-05-06 07:17:23', NULL, '8', '2026-04-26', '0'), (Original) ********************************************************************************************* ('32595', '30', '6472', '1', '2026-08-15 19:30:10', NULL, '8', '2026-04-26', NULL), (Changed) ('32596', '13', '6473', '1', '2026-08-15 19:28:04', NULL, '8', '2026-04-26', NULL), (Changed) ('32597', '10', '6473', '1', '2026-08-15 19:28:04', NULL, '8', '2026-04-26', NULL), (Changed) ********************************************************************************************* ('34130', '13', '6473', '1', '2026-08-15 19:28:04', 'Voided.', '8', '2026-04-26', '0'), (New Addition) ('34131', '10', '6473', '1', '20

Edit Invoice using posted Wiki

I tried to to change an existing Invoice using the procedure posted in the Wiki and the results created parts of the new Invoice with redundant invoice numbers instead of creating unique new numbers. I could not find out why. This is the first time I've tried to change an invoice with this level of software (2.4.19 Default Theme, Church Chart of Accounts). I'm listing all the changes in the DB when I changed one invoice. If any one can help me or even verify that I should see different results and why, then I'll know I did something wrong. Edit Invoice using posted Wiki Results posted below. 0_audit_trail ('32595', '30', '6472', '1', '2026-05-06 07:17:23', NULL, '8', '2026-04-26', '0'), (Original) ('32596', '13', '6473', '1', '2026-05-06 07:17:23', NULL, '8', '2026-04-26', '0'), (Original) ('32597', '10', '6473', '1', '2026-05-06 07:17:23', NULL, '8', '2026-04-26', '0'), (Original) ********************************************************************************************* ('32595', '30', '6472', '1', '2026-08-15 19:30:10', NULL, '8', '2026-04-26', NULL), (Changed) ('32596', '13', '6473', '1', '2026-08-15 19:28:04', NULL, '8', '2026-04-26', NULL), (Changed) ('32597', '10', '6473', '1', '2026-08-15 19:28:04', NULL, '8', '2026-04-26', NULL), (Changed) ********************************************************************************************* ('34130', '13', '6473', '1', '2026-08-15 19:28:04', 'Voided.', '8', '2026-04-26', '0'), (New Addition) ('34131', '10', '6473', '1', '20

Upgrade path for huge leap 2.3.19 -> 2.4.20

I am currently running FA 2.3.19 on Debian 7 (Wheezy) with PHP 5.4. I need to move FA to a new server running Debian 13 (Trixie) and PHP 8.4. From what I have found, the start of the upgrade path should be: FA 2.3.19 -> FA 2.3.26 (old server) FA 2.3.26 -> 2.4.1 (old server, includes database conversions) But what then? I assume at some point FA 2.4.X does not run on PHP 5.4 anymore and the next version 2.4.Y does not run on PHP 8.4 yet. I have not been able to find the PHP requirements for each FA version. I think I need to find 2 versions of FA which - use the same database format - the older version runs on PHP 5.4 - the newer version runs on PHP 8.4 So I would export the database on the older version, followed by an import on the newer version. Does that even exist? Or is there a better way?

Upgrade path for huge leap 2.3.19 -> 2.4.20

I am currently running FA 2.3.19 on Debian 7 (Wheezy) with PHP 5.4. I need to move FA to a new server running Debian 13 (Trixie) and PHP 8.4. From what I have found, the start of the upgrade path should be: FA 2.3.19 -> FA 2.3.26 (old server) FA 2.3.26 -> 2.4.1 (old server, includes database conversions) But what then? I assume at some point FA 2.4.X does not run on PHP 5.4 anymore and the next version 2.4.Y does not run on PHP 8.4 yet. I have not been able to find the PHP requirements for each FA version. I think I need to find 2 versions of FA which - use the same database format - the older version runs on PHP 5.4 - the newer version runs on PHP 8.4 So I would export the database on the older version, followed by an import on the newer version. Does that even exist? Or is there a better way?

Upgrade path for huge leap 2.3.19 -> 2.4.20

I am currently running FA 2.3.19 on Debian 7 (Wheezy) with PHP 5.4. I need to move FA to a new server running Debian 13 (Trixie) and PHP 8.4. From what I have found, the start of the upgrade path should be: FA 2.3.19 -> FA 2.3.26 (old server) FA 2.3.26 -> 2.4.1 (old server, includes database conversions) But what then? I assume at some point FA 2.4.X does not run on PHP 5.4 anymore and the next version 2.4.Y does not run on PHP 8.4 yet. I have not been able to find the PHP requirements for each FA version. I think I need to find 2 versions of FA which - use the same database format - the older version runs on PHP 5.4 - the newer version runs on PHP 8.4 So I would export the database on the older version, followed by an import on the newer version. Does that even exist? Or is there a better way?

Purchase Return Transaction

I have a scenario involving a purchase return transaction; what are the steps for entering this transaction in FrontAccounting? Note: I use the Direct Goods Receipt Entry (D) method, not the Purchase Order Entry (B) method. Any assistance would be appreciated.

Purchase Return Transaction

I have a scenario involving a purchase return transaction; what are the steps for entering this transaction in FrontAccounting? Note: I use the Direct Goods Receipt Entry (D) method, not the Purchase Order Entry (B) method. Any assistance would be appreciated.

Purchase Return Transaction

I have a scenario involving a purchase return transaction; what are the steps for entering this transaction in FrontAccounting? Note: I use the Direct Goods Receipt Entry (D) method, not the Purchase Order Entry (B) method. Any assistance would be appreciated.

115 discussões coletadas desde 31 August 2026. Acompanhe este fórum com uma palavra-chave →