First day trying this version and already having problems, same as with the Beta. After posting a negative receipt it asks, do you want to print now? We say yes and print and it says, "Nothing in range to print". Not sure if there is corrupt data or not and won't know until I can run an integrity check after 5:00pm EST.

When we close the program and re-open we can print the receipts successfully, however, they will not print from the window that pops up after posting.

This is also happening for regular Purchase orders. They will not email or print.

Didn't see this post at the time of doing mine but yes same problem my client is having.

How is it that the full version has been released and the exact same problems that existed in the BETA still exists now, rendering the product unusable and no one even warned us about it? Softrak already knew about this problem and released it anyway. Today, we've lost another 1/2 a day, none of our staff could do their work, customers could not get any information, we could not process any orders, etc. We have had way too many failed attempts at this. 3 integrity checks and repairs later and we have reverted back to POA once again. Please advise when we can safely use this product.

Can you also advise if we'll need further data repair or are the rebuilds in DIC fixing everything now? Here is our integrity check info:

--------------------------------------

Adagio PurchaseOrders: File Integrity

Totals ... 1 error(s) found .................................................... FAILED

Summary

File Integrity ... 1 error(s) found ............................................ FAILED

Finished at: 2013.06.17 12:05

Data Repair Phase

Rebuilding Totals ... Done
Fixed 1 of 1 file integrity errors.
Finished rebuilding integrity errors.
Please repeat Data Integrity Check.

--------------------------------------

Adagio PurchaseOrders: Application Integrity

Outstanding vendor/job costing balances will only be checked
if a day end is performed before running the integrity check.

Purchase Order PO -00004073 is missing all vendor total records.
Purchase Order PO -00004073 has Vendor JO7200 that does not have a total record on line 1
Documents ... 2 error(s) found
Payables Vendor CR1428 has 146.73 on PO, actual is 444.43
Payables Vendor JO7200 has 19000.00 on PO, actual is 9500.00
Payable Vendors ... 2 error(s) found
Summary

Application Integrity ... 4 error(s) found ..................................... FAILED

Finished at: 2013.06.17 12:15

Data Repair Phase

Purchase Order PO -00004073 is missing all vendor total records. Vendor total records added.
Purchase Order PO -00004073 has invalid Vendor JO7200. Please update the document.
Payables Vendor CR1428 on PO updated to 444.43
Payables Vendor JO7200 on PO updated to 9500.00

Fixed 3 of 4 application integrity errors.
Finished rebuilding integrity errors.
Please repeat Data Integrity Check.

--------------------------------------

Summary

Data integrity check was complete with no errors.

Finished at: 2013.06.17 12:26

Hi, all,

It appears that this is either not occurring with all datasets or there is more information required in order for it to be duplicated. I've just entered a negative Quick Receipt using sample data and another client's data I received today for something else and did not experience this issue. When I printed the receipt again (still have the print receipt window open) enabling the 'Reprint receipts already printed' option, I didn't experience the issue then either.

It seems it didn't happen during PwC's training session with his site either, but did occur after. Something is occurring differently either in the steps occurring and print/email options selected or elsewhere. Were you using this site's data during the training session?

Please provide more detail on what is being done.

Susan, is this occurring with positive receipt printing? All negative receipts?

All, are you working in PO8.1B and PO8.1C or just 8.1C? If both, which product created the document in question?

I installed 8.1C and the hotfix POHFP20130608.EXE. I didn't even know it was possible to run 8.1B anymore since 8.1C overwrote my previous installation.

On Monday morning (yesterday), we had 3 users on PO.

• User 1 was receiving both negative and positive and had no issues.
• User 1 also opened an existing receipt that had 2 vendors. Vendor 1 was already invoiced. Vendor 2 was still at the delivery note stage. A line for GST was added with no proration. The tax on the total screen was adjusted by 1 cent. The invoice was posted with no issues other than the tax change was not saved, even though the hot fix was suppose to correct that.
• User 2 was creating PO’s and could not email or print.
• User 3 was receiving negative and could not print.

Hi, Susan,

Thanks for the added information. This sounds like something that is specific to the 'steps/options used' by someone as it isn't occurring all of the time with your data either.

If there's anyway your people (user 2 and 3?) could take note as soon as the problem occurs of what exactly they did and then let us know it could help us and others to duplicate the issue for R&D.

If user 1 were to use user 2 or 3s w/s, do they experience the same issue while logged on as themselves (i.e. not as user 2 or 3)?

PO8.1C installs to a totally different folder (Softrak\PurchaseOrders) than PO8.1B does (Softrak\POWIN)so your original 8.1B install shouldn't be overwritten at all. You are not able to open the same dataset with both PO8.1B and PO8.1C at the same time with the shipping release of PO8.1C though. You are able to open the data with PO8.1B, close it, then open the same data with PO8.1C, close it, etc..

You indicate that the tax change is not saved. Would you elaborate? Where exactly wasn't it saved. I too edited the tax for the 2nd vendor (on the 2nd receipt for the PO) and changed it by 1 cent. The correct, adjusted amount was sent to both AP and GL. And, in PO, I see the correct information in the Data Flow and inquiry.

I will test this some more. As always, any more detail you can provide is appreciated.

Hello Softrak Support,

Okay I didn't realize that POA was 8.1B. I was thinking that you meant PO Beta was 8.1B. So to answer your original question, we finished off Friday with POA 8.1B and started out on Monday morning with PO 8.1C. After the crash, we reverted to POA 8.1B. Everything was fine on Friday with 8.1B as it always is. The problems occurred when posting the first PO of the day on Monday morning in PO 8.1C.

User 2, could not email or print the PO. This is the document that later was found to be missing total records. It was a very basic PO with only one vendor and one item. Since that PO alone should not have been a problem, maybe it has something to do with posting a PO while other users are simultaneously posting receipts and/or invoices? Or maybe it was User 1 who caused the problem when they posted a receipt with 3 items with negative quantities and the same 3 items on the same receipt with positive quantities. However, this receipt posted and printed successfully. Or it could have been the next thing that User 1 did which was opening an existing Receipt that had been created previously in POA and was already invoiced for Vendor 1 lines but not for Vendor 2 lines. Vendor 2 had 2 misc charges that had been received with proration at relative value and were at the del note stage. Those 2 lines were posted as an invoice along with a 3rd misc charge that was added at the time of invoicing to Vendor 2 with no proration. Everything appeared normal when posting this invoice, but maybe the complexity of this post is what led to a problem for the next person to post (i.e. User 2 PO, that would not print and lost it's total records). User 3 was able to post but not print the next 3 negative receipts.

I can't specifically answer your question about user 1 going to user 2 workstation and logging in as user 1, etc., because we don't operate that way. Everyone has their own computer and workstation and they log in as themselves.

Hope this helps. We're looking forward to a solution soon.

I actually opened a back up of our data last night and re-created the same entries as described above. I did them one at a time with one user and there were no issues. This leads me to think that the problem is more likely related to users posting PO's/Receipts/Invoices simultaneously.

Hi, Susan,

Thank you for the added detail. We'll do some extra testing with the multi-user environment. Although testing has already been done in this area, it's doubtful that your exact situation was tested. Getting this set up may take some time though. I will come back to the issue when we've had time to complete some more testing.

Other than the Receipt that User 1 posted for Vendor 2 that had previously been Receipt-DN only, all other documents were created in PO8.1C?

Yes.

So you know, in PwCs case, their problem was resolved by editing their AP8.1E vendors and ensuring that, on the Payee/PO tab, in the PO Print Options section, the appropriate Send Methods were set.

Your users may all be using the same dataset but it could be worthwhile checking to ensure that the vendors (on the documents for which print problems were experienced) have these set also.

Do you mean the 3 check marks in Send Method? Or the Print/Fax/Email specs?

I just checked and here is what I found:

All vendors have all 3 send methods check marked.

All vendors are blank for all 3 specs.

It was the Send method.

Again, thanks for the added info.

Hi, Susan,

We've tried to duplicate this and for us, even when we all post these documents at the same time, the proper locking occurs (and messages are received by the users affected). Each user is able to print their documents. No integrity errors are created.

It would seem that either some steps are missing and/or our network environment is different so we are unable to duplicate the issue.

You indicated earlier in this thread that, at one point, you restored the backup from before last Monday and the move to 8.1C so you could test this out as a single user. It may be possible that, if this is a program problem and we had this PO related data, we would be able to duplicate the issue assuming the steps we are following are exactly what occurred at your site.

For now, however, we have not been able to duplicate the issue.

Can you confirm if there are any other locations who are using PO 8.1C with multiple users?

Hi Susan

We are, but there are only two of us, and it doesn't sound like we use it as intensely as you do. It's not often that we are on at the same time, but when we are we haven't seen had any trouble. I was going to enter PO's and do some receiving today but I'll wait til tomorrow when the other person is in and see if we have any problems.

Thanks Mike! We really want to move to the new PO but can't resolve this issue.

We are trying again here today. If we partially receive a PO and then go back to print the outstanding items on the PO, it says, "nothing in range to print". If we check "reprint purchase orders already printed" then it prints okay. Is this normal behaviour? Shouldn't we be able to print the outstanding items on the PO without having to select reprint?

Hi Susan,

I don't think so.

A purchase order is an authorizing document when sent to a vendor. Just receiving goods on a PO doesn't mean that you'd want to send it to your supplier again. They already have the original and know they have other items to fulfill.

Comments welcome.

Okay. We want to print the outstanding items so that we know what we're waiting for and can follow up. No problem if we have to select "reprint purchase orders already printed". Just making sure that it's not a data problem since the error we always get before data corruption is "nothing in range to print". This message scares us every time we see it.

Susan,

Why wouldn't you print the the 'Outstanding PO Items' report under transaction reports instead? Why would you want to print the whole purchase order again?

Andrew,

There are times when you have to reprint the PO (like after spilling coffee on it). Couldn't it be set-up like Order Entry where if you re-print an invoice from the invoice screen the reprint invoices option is automatically checked?

We are crashed..

Can someone from Softrak tech support please call us? I tried calling but only getting voice mail. I suppose it's still early out your way. We have stopped working and left the error on our screen so that we can retrace our steps with you. 613-392-3875

Hello Susan,

Sorry, this isn't a service that we offer through the Forum.

I thought you might want to know what is causing your software to crash since you weren't able to duplicate the issue at your end. Apparently you're not interested?

We're very interested and will work closely with your Adagio Consultant to isolate the problem, as we do with all our shipping products.

Hi Susan

We finished all our receiving and invoicing this morning and had no problems but one (see below). I had the other person enter a vendors' invoice while I entered a receipt for the same vendor at the same time; no problems. Have you considered that it may be a network problem? From the following thread: http://www.softrak.com/ubbthreads/ubbthr...vendo#Post37171 Andrew stated that the version is slower than the old POA. Could there be a bottleneck somewhere that's causing the crashes? I had a bad switch a couple of months ago that just brought everything to a crawl (and it was only one bad port on the switch) and we have a Gigabit network. Just an idea.

I did receive the following error when entering a receipt for the first time, but it was a case of going to fast. I use the keyboard, so alt-I, alt-D, and Enter take me to the first item. I can press those keys faster than the system can load so I receive the following error: