[DVigliatore]

Is this going to be addressed in 2.09? Is it still planned to be released by the end of this month?

Thanks,

[DVigliatore]

When paying multiple invoices, the system usually prints the cheque and voids cheques subsequent to it when needed.

Currently when we know we are paying suppliers with multiple invoices, we make the destination to display, so that the check stub is sent to excel; at which point the cheque and the stub is adjusted manually. As we’ve noticed that too many cheques are voided when we pay 30 or 40 invoices.

We also tried only ‘posting’ the payment of the multiple invoices instead of ‘posting and printing’; then we went to the bank payment journal and tried to print the cheque. Same result.

This only happens when we are paying more than 7 invoices on 1 check; and this happens several times a week.

Is there a more efficient way of doing this? Printing the check without the stub details and then printing the stub alone or separate form the physical cheque stub on a regular sheet of paper?

Thanks,

[DVigliatore]

Does the external drive need to be used only for the data on the server? Not the workstations?

[DVigliatore]

So there’s no way of paying the balance outstanding without giving somone a larger edit date time span? Instead of giving some 1 month, I would have to give them 3 months?

[DVigliatore]

Just opened NV2 and made sure that the 1 account that we locked down worked properly. It only works if we go through Account…Accounts Payable..to the supplier..all the way to the pink screen as we discussed yesterday.

When we go to the Purchase Invoice Journal to post, which is where we do our postings from, it doesn’t work; even though I’m pretty sure it did yesterday when we walked through it. I tried doing this as the Administator and a a regular user…neither works. Any ideas?

Also, if we get this to work, and in the future we need to change the ‘root’ account to be chosen, how can we undo what we’ve ‘locked’ and change it to another account…I forgot to ask you this yesterday.

I tried changing it through the same methodology as we discussed and it crashes NV2 as it did yesterday.

Please let me know if you know why it doesn’t allow the posting with the ‘locked’ account through the PI journal.

Thanks,

[DVigliatore]

We currently use that method when we are posting Sales Invoices for our customers.

The concern on our end is invoices being posted and paid for our suppliers through the Purchase Invoice Journal.

[DVigliatore]

Sorry…the same error message occurs no matter what journal I go through.

Please let me know if I am doing something wrong.

Thanks again,

[DVigliatore]

I just realized that I followed your instructions and went through the PI journal and then details.

I will try through the Vendor account.

[DVigliatore]

I have tried what you’ve suggested and as soon as I press F3 to display the Select Pick Root window…NV2 crashes.

The following error message appears:

.text {Encountered bug “314120040830144312” while running “d:/home/dvigliatore/computer/nv2/nv20.exe” (2.08.8.20060801) on computer “boltonrailings”.}
.help_id 314120050312171551
/a2 {
.text {Encountered bug “314120040830144312” while running d:/home/dvigliatore/computer/nv2/nv20.exe on computer “boltonrailings”.}
.priority bug
.log {
.type bug
.date 20061011075253
.nameofexecutable d:/home/dvigliatore/computer/nv2/nv20.exe
.version 2.08.8.20060801
.hostname boltonrailings
.stack {
.5 {::qw::bug 314120040830144312 {Attempted to call method “” on /OBJECT/SYSTEM/WINDOW/SCROLLED/TABLE/NOTES/COLUMN_DEFINE/REFERENCE/1160566987_112875.client with args “expand_path /OBJECT/NEWVIEWS/ACCOUNT”.}}
.4 {{} expand_path /OBJECT/NEWVIEWS/ACCOUNT}
.3 edit_assist_pick_root
.2 edit_assist
.1 {reference_pick {.windowPath .20.25.75.7a.81.86.87.8c .type 2 .serialNumber 1613 .send -1 .state 8 .subWindowHex 0x00000000 .time 1100822671 .x 279 .y 150 .keyCode 114 .asciiCharacter {} .keySymbolString F3 .keySymbolDecimal 65472}}
}
}
.bug_id 314120040830144312
/a1 {
.text {Attempted to call method “” on /OBJECT/SYSTEM/WINDOW/SCROLLED/TABLE/NOTES/COLUMN_DEFINE/REFERENCE/1160566987_112875.client with args “expand_path /OBJECT/NEWVIEWS/ACCOUNT”.}
}
}

[DVigliatore]

So I guess this will be fixed in version 2.09.

Will we have the option of setting the increment from either the root reference journal or the sub journal? Or only the root refernce journal. (as this may help in this case but may not help in other cases)

[DVigliatore]

Hi Dave,

Please post your success or failure with your approach, I am interested to know the result so that I can consider a change in hardware setup/configuration as we too, are having speed issues.

Thanks,

[DVigliatore]

We had already thought of that…the only reason that will not work is that all my invoices, whether they are supply only or supply and install, must follow the same numbering sequence. It’s not pratical to have 2 different numbering systems.

Maybe we should chat about this one.

thanks,

[DVigliatore]

New help file in 2.06 addressed this

[Author]

Posts