PayWindow Update process broken

[Louis Puster]

I am a brand new user of PayWindow running it on Windows XP using Multiple user/Multiple computer setup. This means that the tax and data files are on my server and accessed via UNC paths. I finally got PayWindow to accept this setup (it was difficult due to the strange setup procedure). When I installed an update, the software updated and this deleted the location information of these files. When I tried to set them up again, I got the EInOutError, Unable to create directory. It appears that PayWindow was trying to use the blank field as the path to the tax or data rather than simply opening a file selection dialog so that I could point out the files. It's not a permission problem, I am running as Admin under XP. When the error occurred, PayWindow created a bugreport file and offered to send it. However, it was unable to send it! I saved it as a file and when I tried to re-do the setup, I got stuck in the Tax Table Maintenance window. I can click Previous and go back as far as "Welcome to Tax Table Setup". At this point neither Previous nor Cancel does anything. I can click Next and step as far as "Your Selected Option is:". At this point neither Next nor Cancel does anything. Since the Tax Table Maintenance window is modal, I cannot close PayWindow the normal way. Why must I use the Task Manager to kill it?

I feel that PayWindow has some serious human factor problems. The File menu lacks an "Open" which would allow a user to select the desired data file and there should be a setup window where the tax file location would be an input field. Naturally, a software or tax file update should not destroy the setup.

I understand that PayWindow has been in development for awhile, so I assume these bugs are a new development and I am willing to help you any way I can to resolve these issues. In particular, I could give you a detailed ****ysis of my perceived human factor problems, but I don't want to waste my time if my efforts will not be taken seriously.

Louis.

[Paul Mayer]

Because the network choices we had for the tax tables in the past was causing an enormous support problem for the majority of our customers (non-network users), we pulled the old tax table setup out and now install the tax tables by default to the local machine in the "My Documents\PayWindow Tax Files" folder.

We are even encouraging our network users to do the same because of the above problem.

There is a File Open selection. It is "File | Open Company" it's been there ever since we started. With accountants having many company files that we allow at no extra cost, it's a very well used menu selection.

86

[Louis Puster]

Thank you. I later found I was stuck in that window because the Debug information was being displayed in a window behind the others. (Either the Cancel button should have closed it or the debug window being open should not have affected the Tax Table Maintenance window.) After the update, when I exited and restarted PayWindow, it found the databases. Perhaps restarting PayWindow after an update should be documented.

Yes, there is an Open Company in the File menu, however it is always grayed out, along with Logout, Passwords, Close Company, and Backup Company.

I just discovered that they are no longer grayed out after I click Next. I expected Open Company would be available right from the outset. It shouldn't be necessary to open the default company in order to close it and open another company. What would happen if the default company was blank or wrong (because the database had been moved)? Would I then be stuck, unable to open the company file and unable to click next?

Are you saying that I should maintain a separate tax table in each workstation? I was hoping to use a central table to insure everyone was using the same one.

Why can't the red X in the upper right corner of the Welcome window do the same thing as the Exit button?

Louis.

[Paul Mayer]

The debug tool must have popped up because it could not find the tax tables. You were most likely clicking something when it popped up and sent it behind the Window that your mouse gave focus to.

Yes, you figured out that you cannot access menu items because you were not logged into the program yet.

If you'd used the Tutorials we provide, the first page of the first Tutorial in the list shows PayWindow waiting for you to click the "Next" button and the "information message" reads as follows:

"When you start PayWindow, you will be asked to select the date to use for today's payroll.

You may also select a Company file from the file pick list if you manage multiple companies. The last used file will be the default that is selected.

Clicking the Next will enter the program."

So as you can see, you really can't get stuck because you can still select a company file using the tools in that page to open the File Open Dialog and locate and select your database.

We block the Red X as too many customers through the years accidentally use that and lost what they were in the middle of.

Features like that are added after a number of users have had problems and we adapt the program to reduce errors like that from happening.

[Louis Puster]

I had opened the debug details on purpose, but never dreamed that having that window open would interfere with anything.

"We block the Red X as too many customers through the years accidentally use that and lost what they were in the middle of."

But the Red X is not blocked when I am in the middle of entering a transaction, even with unsaved data on the screen, but it is blocked in the welcome window, before I log into the program. Does this make sense? (I have disabled the quit prompt.)

Louis.

[Paul Mayer]

I had opened the debug details on purpose, but never dreamed that having that window open would interfere with anything.

"We block the Red X as too many customers through the years accidentally use that and lost what they were in the middle of."

But the Red X is not blocked when I am in the middle of entering a transaction, even with unsaved data on the screen, but it is blocked in the welcome window, before I log into the program. Does this make sense? (I have disabled the quit prompt.)

If the program should get an error it cannot recover from and continue, the Debug tool takes over and freezes the state of the program and gives you several choices. Send us the bug report, save the bug report or view the bug report. Until you perform one of the actions or have the tool either continue (not recommended) or shut down the program, you are locked out. When you send or save the bug report, it takes a snapshot of what happened to help us diagnose the problem.

On startup, you are in a mode until you actually click the "Next" button where we cannot allow the program to close without proper handling of the state of PayWindow. The red X will not allow us to do what is necessary like we can when you close normally. And in that state, you are not in PayWindow yet, PayWindow is waiting for you to click that Next Button to insert the date and the file to use. Steps that we cannot let you abandon since we also have opened the initialization file and are waiting to poke the data we need into.

Once past that point in time, you can click the Red X to quit or abandon anything you want.