Sage 100

Has anyone discovered the secret to getting focus on the login screen within MAS? I'm nearly positive this is related to specific versions of OS - because not all users see this. It's rather troubling when we sell an ""upgrade"" and have to back pedal and apologize for things which don't work smoothly or require a lot of manual intervention such as tweaking paperless drivers that often don't setup properly on Win 7, manually copying CRPE32.DLL and chasing down C++ executables that need to be installed in order for a workstation to run. I don't claim this happens on every single install - but in the last half dozen I did there were enough problems that I'm wiling to state that it's a global Sage issue. I'm also unsure why the Sage install routine can't be designed to catch DLL files which do not register due to lack of permissions. I understand that users need permission to install these things - however wouldn't it be better manners for Sage to flag any failed DLL installs rather than have the user discover these after we leave the site? Question from customer - anyone found a cure for this?: Is there a setting that allows you to start typing the user and password in the MAS90 log in screen without having to click on it first. I do not remember having to do this in v4.20. In v4.50 when I click on the MAS90 icon to start it up the log in screen pops up but I can not start typing into it until I have click on the log in screen. Just an extra step that not all of our units require.

On he login screen coming up without focus, I have seen that from time to time in all 4.x versions of MAS. What's really odd is the sample login screen that M$ provides for Visual Basic.net apps tends to do the same thing.

It's all about the ""Harvest"" or TLTF

Instead of flagging DLL's lacking permission, why even start the process if permissions are lacking?

The installer isn't all under Sage's control. There are the Crystal run times and the Amyuni installer.

So @RobertWood what you are saying is that Crystal and Amyuni are not telling us that the .dll's did not install correctly and if that is right are other software using Crystal and Amyuni having the same issue's with the .dll's as we are?

That is exactly what I'm saying.

Thanks @RobertWood