Search results

MajP, General date shows seconds. For this purpose, that's visual clutter, and what I'm hoping to get rid of. Not sure why I didn't get any notifications re these later updates - thanks everyone!

Minty I think that expression would be read only, so no edits. Pat, yes; I am hoping for some voodo formatting technique. What I'm after could have been something that msft anticipated, but as far as I can tell there is nothing in the Access kit that allows. If I find a way I'll post it back here.

In a datasheet, is there a way to format a datetime value with hour and minute only (no seconds) if there is a stored time value, but if the value stored is only a date, show as mm/dd/yyyy? The goal is to have these outcomes: enter a plain date 10/11/2023, show 10/11/2023 enter a date time...

amorosik can you give us some examples of 'other' terminal servers that you've found work well. I have mild exposure to tsplus, which I found worked well as far as I took it, and does work with windows 10 etc. The issue I mentioned is between Office 365 (at least) and server OS, so unless...

It's all guesswork on my part, but if the perpetual licensed versions of office are still ok on server os, it'd make sense for the runtime to also remain viable. If it works out like that, it's not really the end of the road.

You mean 1 to go, right <g>?

I'll try though I've not been able to post with urls here before yeah can't do that. maybe search for Office Apps Won't Run on Windows Server After October 2025 (where I first ran into it) Microsoft 365 Apps migration from Windows Server - Deploy Office (msft site)

But bear in mind, at least according to what I've read, you won't be able to deploy office 365 to any modern msft server os starting in 2025. That means rds etc will no longer be viable methods of deploying Office 365 Access applications. They still may allow perpertual licensed versions of...

I've been attempting to use ODT to download and install a most recent version of office 365 Office 2019, mostly for Access. I find the versions numbers quite baffling. Supposedly one can use the ODT with the tag targetversion to spec a specific build and version. The FMS page is maybe the best...

Yes that's the main mystery, why the debug from cmd variable in RunCMD() executes fine in command prompt but fails when RunCMD tries it. I can't post the screenshot without altering it because of org name embedded etc. Thanks!

Right...both of the lines I posted work in commend prompt. The upper one that starts with cmd.exe /C is an exactly copy of what RunCMD() debug output for the cmd variable contains. The lower one is simply a reduction of the original, as I figured the leading cmd.exe /C was redundant when entered...

I know it looks strange, doesn't it? But the full structure that debug emits does seem to make sense, or at least it could make sense. After the leading cmd.exe /C the entire string is wrapped with a pair of doublequotes, and inside that string two other strings are wrapped in doublequotes...

Two boneheads are better than one...I'll continue to experiment and will report back if any progress. It is a nice bit of code, appreciate that you put it up here.

ironfelix, thanks for posting this code, it's a real find. I am having issues and would like your input. As I've understood from your examples, one may either stuff the parameters into the Path variable, or else send as an array via ParamArray(). In my testing I've found cases where in calling...