01-06-2018, 10:15 AM,
|
|
briantmg
Member
|
Posts: 24
Threads: 13
Joined: Jul 2017
|
|
Enter Payment to Vendor
I tried to enter a payment to a vendor and ran into a couple of problems:
1) It shows the invoices that need to be paid and I can click in a box to include those invoices in the payment. however, when I press "Update", nothing happens.
2) I tried to just enter the information into "Supplier Transactions Payment Entry" section.
However, I get this error:
Database Error 1054 : Cannot insert a payment transaction against the supplier because
Unknown column 'chequeno' in 'field list'
Database SQL Failure : Cannot insert a payment transaction against the supplier using the SQL
INSERT INTO supptrans ( transno, type, supplierno, trandate, inputdate, suppreference, rate, ovamount, transtext, chequeno ) VALUES ('147', 22,'4114','2018-01-05','2018-01-05 17-45-51','Cash','566','-405761','', '')
In looking at the database, I do not have the column chequeno in the supptrans table.
Should I put this column in or is it an error in the script?
|
|
01-07-2018, 02:06 AM,
|
|
briantmg
Member
|
Posts: 24
Threads: 13
Joined: Jul 2017
|
|
RE: Enter Payment to Vendor
After further investigation, I see that I need to update my database for the newest version of that script to work
|
|
01-07-2018, 03:55 AM,
|
|
briantmg
Member
|
Posts: 24
Threads: 13
Joined: Jul 2017
|
|
RE: Enter Payment to Vendor
Yes, I downloaded the latest script from SVN the other day. This morning I checked the upgrade database file and noticed the fields are added in the next upgrade. I updated my database. It seemed to work fine.
However the update button when clicking on the invoices in the Payments.php script still does not do anything.
|
|
01-09-2018, 01:25 AM,
|
|
VortecCPI
Paul Becker
|
Posts: 751
Threads: 211
Joined: Apr 2017
|
|
RE: Enter Payment to Vendor
(01-08-2018, 08:10 AM)falkoner Wrote: What we should really do is return to the days when we kept a stable branch. That is a branch whose root is the last release, but only has bug fixes applied to it and none of the new features. Then people can download scripts with bug fixes without worrying that they corrupt their current code base with new features which could block other areas. Perhaps something you could consider running Paul (Thursby)?
Tim
I agree that fixes should be separate from new and/or extended features. This would prevent confusion, which we often see with respect to DB schema for example.
It appears we don't really use the typical SVN Tag/Branch/Trunk schema so perhaps we should include fixes in the trunk and new/extended features only in a coming-release branch.
While this is more work I think it would benefit all involved.
https://www.linkedin.com/in/eclipsepaulbecker
|
|
|