As soon as I put on the AR 9.0B upgrade for a client previously using AR 9.0A, the runtime parameters /d and /e stopped working. In other words, my client has five shortcuts, one for each AR dataset, each with a /d and /e parameter pointing to the datapath and extension of that dataset. However, when they choose a different shortcut than the one they were just in, the one they were just in appears.

This is a standalone C: drive install. I checked and nothing has changed with regards to the shortcuts, and the syntax is proper.

Steve

Hi, Steve,

I can duplicate this behaviour, but only if the second (third or fourth, etc.) is a clone of the first (i.e. when I make the second shortcut, I do so by copying the first). It seems that they are literally joined. When I make a change to one, that same change (be it parameter or name) is automatically made to the other.

However, if I drill down to the executable and create a new shortcut from there, it stands alone and changes I make to it (eg. parameters and/or name) remain with it alone and have no affect on the first shortcut.

That's nice to know, but since most people copy existing shortcuts, you should gear up for a slew of support calls on this unless you fix it.

I'm assuming this is now on your list to fix?

Your workaround didn't work.

I logged on to my client's workstation, found Receivables.EXE in the \Softrak\Receivables folder, and sent the shortcut to the desktop. I then renamed the shortcut and copied the Target line from the "bad" shortcut to this new one.

It still ignored the /d and /e parameters, and tried to open a different dataset, the one that was most recently opened.

What now?

Steve

Hi, Steve,

We haven't been able to duplicate this latest problem with the information provided so far.

- Are you using any other parameters on the shortcut than the /d and /e parameters?
- What happens if first delete the 'bad' shortcut and you manually 'type' the parameters into the new shortcut?
- What is the OS of the w/s in question? I'm using XP SP3 and we've tried to duplicate on a Vista Business SP1 also. We have others that could be used to test.
- When you get to the Receivables login window, do you see the Remember user name and/or Remember user password fields? Which?
- If you see one and/or the other, is one and/or the other option turned on?

Let me know.

I'll answer what I can, and find out the other answers later.

The /u parameter is also being used
The remember user name and remember user password fields are there but are not turned on. Although you didn't ask, there is no password.
I don't know what version of OS for sure, but it isn't Win7. I think it is XP SP3. I'll find out
I will the delete and manual typing of the parameters.

Steve

Hi, Steve,

As she doesn't use a password, please also try adding the /p parameter but not entering the actual password. Does it open the correct dataset now?

I believe you'll find that it works the way you expect if you tick the "remember user name" box. The login seems to want to use the previously opened database if the user name is not being remembered.

I'm finding this thread quite interesting as I've been having an issue with the /d and /e parameters for quite a while now - long before AR 9.0B.

My issues started when the modules started rolling out with the, then "new", sign on window - the one that started having the "Remember user name" check box and where "the saved information is based on your Windows authenticated user name". Ever since then, I realised at a number of sites that the /d and /e parameters were being ignored. I thought that for some reason this was the desired behaviour of the "new" sign on window and rather than giving users multiple shortcuts, I just started telling them to choose the correct company from the "previously opened" list.

Personally I believe that the startup parameters should overide all else but never got around to complaining about it Now, that I read this, I'm realising that it wasn't the "desired" behaviour and that I should have mentioned it earlier. I'm very surprised that it's only now surfaced though as it's been several months to a year that this started happening at my clients. Could there be something different about my configuration ? Hmmm... Not that it may have any direct bearing on the issue, but I always implement the setting to remove the "Remember password" check box from the sign on window - maybe others aren't doing that.

Pete

The login is presenting the last accessed database for the application for specific combinations of parameters and "remember" settings. We agree that the command line parameters should override everything else. It's surprising that this hasn't been mentioned earlier. We've never noticed it here. It's not an AR 9.0B problem.