Search results

Not weird at all. Every day is a weekday. - At least, I'm not aware of any day that is not part of the week. You confuse weekday and workday, which Microsoft explicitly addresses in the documentation of the VBA DateAdd function:

The data types are different Varchar vs. NVarchar. That could cause the difference. (just on the phone, cannot verify, just a guess.)

This should be the default and shouldn't need to be explicitly ensured. Can you post the stored procedure's parameter definition and your code calling the SP?

With the 0x prefix SQL Server indicates that the value is of the data type (Var)binary. - This is expected. The completely different return value for the hashing of @pPassword must have a reason outside of the shown code. I would guess, that the value of @pPassword is different from the assumed...

Of course, the computation of the hash during password verification must follow the same rules as the original hash computation. I've got the impression, that in the current context of this thread it is more important to clarify the basic principle instead of addressing all potential details...

A dedicated login dialog for the application may not be necessary. If a Computer is only used by the one distinct person being logged into Windows, then any further login dialog would be redundant and can be replaced by just using the Windows user name without further user interaction. SQL...

If the user has been authenticated by Windows auth, it should not be required to authenticate the very same user again in the app. A user enters their username and password. You compute the hash of what the user entered for their password. You run a query against your user/password-hash table...

But the person being authenticated through Windows will be the very same person authenticating with your app, won't they? Your very first sentence in this thread was: So, I, and probably several other people, assumed you knew how to compute a hash. SQL Server has the built-in Hashbytes...

You generate the SHA-512 hash of whatever the user entered for the password when trying to log in. If it is identical to the stored hash in the database table, the user entered the correct password. Nonetheless, @theDBguy has a valid point. Your users must authenticate to SQL Server anyway, so...

I don't think this is possible.

Yes, I think so. Wayne's Mousehook code is not your typical 32to64bit conversion. The module includes a COM class in assembly language that is embedded in a string in the module and loaded into memory at runtime. Unless you feel qualified to adapt or replace the assembler code for 64bit you...

You can use the Windows API to encrypt/decrypt data based on the currently logged in Windows user account. This will not require entering a password. Warning: This is not suitable to encrypt shared or long-term data. The encryption is tied to one specific account and resetting the account's...

Yes. I believe every three months a new evaluation image will be released with an expiration date 6 months in the future. Once expiration date is reached, you can still use the VM, but it will then automatically shut down after one hour of use.

There is an ampersand missing: shellCmd = strQuote & strSFTPDir & "winscp.exe" & strQuote & " " & strQuote & strCommand & strQuote

Did you quote the path to WinScp, as suggested by @ComputerVersteher in #12. If not, it is not weird, but rather expected.

If you have an existing OS image file for the virtualization software of your choice you can of course use that one. - But from your questions it's fairly obvious that you don't. If you don't have an existing OS image file, you must create it. Create a new VM with a new virtual disk file in...

At any place that sells Windows licenses. Maybe you got a MSDN subscription, which includes Windows licenses? You create the VM yourself using the virtualization software of your choice. Microsoft Hyper-V is included with Windows Pro, you just need to install/activate it explicitly as it is an...

Just run winscp.exe, exactly as you did before.

Yes! No! Winscp.com was only meant as a tool to manually test your commands.

Then you should change the remote directory using the cd command not the local directory. PS: Also pay attention to @ComputerVersteher's comment regarding the blanks in the path! There is a WinScp.com file in the WinScp directory. This is an interactive command line client, which allows you to...