View Full Version : Data and Tax Table Location
TheBigZ
07-07-2009, 09:49 PM
If I choose 'Multiple-Computers, Multiple Users Mode' (Option 3), I'm not able to browse to a directory.
I'm consolidating a couple computers & I'm moving Paywindow to the machine with all the tax & accounting data on it. So I did a fresh install of Paywindow on that box. But when I try to set up the default path, the button (the one with ...) that usually allows me to browse to a directory, doesn't do anything. The only choice I have there that does anything is to 'Map Network Drive'. I'm running as admin, so it shouldn't be that. And if I do go ahead & map the drive (which I don't think I really need to do, as it's a local drive), I still can't browse to it.
Something I'm doing wrong, or a buglet?
edit: Happens if I choose Setup Tax Table, or Setup (Default) Data Directory.
Paul Mayer
07-07-2009, 10:31 PM
Thanks for the report, something broke as I just tried it myself. It will be fixed in the next release.
TheBigZ
07-07-2009, 11:31 PM
Glad it wasn't me for a change. ;)
Paul Mayer
07-08-2009, 05:49 PM
This is fixed in 7.0.33.
TheBigZ
07-14-2009, 04:27 PM
I can now set the data path. However, there seem to be a few places in the program that are ignoring the path. For example, when I choose File - Open Company or File - New Company... it's opening at \Documents\PayWindow Data Files as opposed to the directory that's been assigned. Same thing when I preview 941's, it's prompting to save to the default di & not the dir that's been set up. I'm guessing it's happening everywhere except the open company dialog box that comes up when you open PayWindow.
Now I've run into the printing in Vista problem again. I remember encountering this when I changed my wife's machine from XP to Vista, but I thought there was a fix for that in the past? Basically, I can't print anything from within PayWindow... it tells me I need to install a printer first. Can't even print the 941 pdf from within the preview. I can print from any other app on the machine. I can even bring up Adobe seperately & open the 941 pdf & print it, just not from PayWindow. I've been wracking my brain for days trying to remember how this got solved on my wife's machine.
Paul Mayer
07-14-2009, 04:43 PM
I've got the developer checking all last path used settings since I noticed the same thing too.
Your printer solution is number two or three in the list of FAQS:
http://zpay.com/vbulletin/showthread.php?t=2310
TheBigZ
07-20-2009, 09:57 PM
Welp. My printer driver was right, but I dl'd it again from HP & reinstalled, just to be safe. I made the changes to the security tab as suggested by the FAQ. The printer is connected directly to a switch, which is in turn connected to a router, so there's no "server" to make sure I'm logged into. I'm pretty sure you're not saying I need to be logged into the router itself to print.
In the end, the only thing that let me print was to turn off UAC. While I'm no fan of UAC in general terms, I'm also not thrilled to be forced to turn it off just so one specific app can print properly. I know how you love to hear stuff like this, but when no other app on this machine, or anywhere else on the network has a problem with printing, there can really only be one culprit, and it's not the UAC.
Paul Mayer
07-20-2009, 10:21 PM
That fix that we posted is the only one we found on Google that would work consistently until you came along with that switching installation. When searching Google you will see there are 4,790,000 hits for the "Printer selected is not valid" problem.
If you go through those hits, two things I've found are in common. They are mostly HP printers, and mostly applications written in Delphi. PayWindow is written in Delphi.
We really do not have a definite cause as you can see with that may people having the same problem.
I do know that you would most likely have good results with a printer attached direct to the computer and not a switch box. Unfortunately, thousands of software developers just have not been able to get 100% reliability with that problem as you saw in the Google hits on the problem.
All I can say is sorry... :(
Powered by vBulletin® Version 4.2.5 Copyright © 2025 vBulletin Solutions Inc. All rights reserved.