I can guarantee that it's not as bad as the mistakes I've been making recentlygbilley wrote: ↑Tue Jun 29, 2021 11:18 am OMG, I think I committed the worst rookie coding mistake in the book! And once again, it was your latest screen shot that showed me the errors of my ways.
My error was assuming (or worse, not even considering) that everyone uses a one-word Windows user name (which just shows you how old-school I am).
I know what you mean about the usernames though. I never used my real name, let alone my full name, everything was Tippon. It's only since Windows 10 linked the licensing to Microsoft accounts that it changed. I didn't even realise until after setup finished and I hadn't put in a username.
Just to confirm, the new code replaces this bit, yeah?gbilley wrote: ↑Tue Jun 29, 2021 11:18 am If my realization is correct, using the following script in freedbSubmitter.vbs should fix the problem:
If this fix works, my apologies to you and all the others who've wasted time on my faulty scripts. But my thanks and appreciation to you for sticking things out and helping me find a solution.Code: Select all
Sub launchSubmitter Dim objShell, htaPath, cmd htaPath = "freedbSubmitter\freedbSubmitter.hta" Set objShell = CreateObject("WScript.Shell") cmd = """" & SDB.ScriptsPath & htaPath & """" objShell.Run cmd, 1, False Set objShell = Nothing End Sub
If the above fix doesn't work, then I'm totally befuddled.
Code: Select all
Sub launchSubmitter
Dim objShell, htaPath
htaPath = "freedbSubmitter\freedbSubmitter.hta"
Set objShell = CreateObject("WScript.Shell")
objShell.Run SDB.ScriptsPath & htaPath, 1, False
Set objShell = Nothing
End Sub