Recent content by isladogs

That was me dredging up long buried memories. In one sense close.... but in another completely wrong. 🙄 In Windows, that is just a shortcut! Delete the shortcut...the file still works but of course the reverse isn't true

I can replicate that also but only in 32-bit Access with 64-bit Windows. None of the msj*.dll files shown below appear when viewed in File Explorer I think the reason is that there is actually only one copy of these files and that registry redirection is involved in a mixed bitness system...

Yes I agree about SYSWOW64. However I repeated the test on 32-bit Access in 64-bit Win 10 Again the only (non-archived) copy of the msjtes40.dll file was in the SYSWOW64 folder and was the same version v4.00.9801.0 dated 07/12/2019. Once again, the reference library loaded without error. Not...

@arnelgp has very accurately described how my 'kickout' system works. Once the system has been locked, new users cannot login to the FE. A different warning dialog appears at startup and the app closes automatically. In my apps, the boolean Kickout field is in a linked SQL Server table...

Following your prompt, I just successfully added the Jet Expression Service Type Library as a reference in 64-bit Access 365: Perhaps it worked for me because in Win 10, I have an older version v4.00.9801.0 dated 07/12/2019. There isn't a newer version of the file anywhere else on my system

This is my deliberately over-the-top form which is displayed during the countdown to forcibly closing the app for essential maintenance. It was designed like that so it wouldn't be ignored. Users can temporarily hide the form to complete their work but it returns every 30 seconds until shutdown

Adam Waller gave a truly inspirational presentation to the Access Europe User Group on Wed 3 Sept where he demonstrated the power of version control for sole developers (as well as for teams) The video of the session is now available on YouTube: Adam showed how his free open-source...

Not that its relevant to the OP of this thread but I just tested this. You can do that as well

It IS easy providing you are aware of and deal with the issues I mentioned in post #17. I do this regularly converting utility files such as my Access Version checker add-in from A365 to A2000 / A2003 and sometimes from there back to A2007 ACCDB. It isn't something that needs or would benefit...

That’s the reason why many of us have included code to force out users after a period of inactivity. I usually allow 20 minutes with a warning just before that expires

Agreed though I allow a shorter interval - maybe 30 seconds. Providing the user takes any action within the specified time interval, the countdown timer automatically resets to zero

I disagree. I often create MDB files from 64-bit Access 365. I then open them in A365 to check they still work correctly. I then open them in an A2003 VM or A2000 VM with no problems whatsoever. Perhaps I'm missing something in your comment but I don't see the problem (with my earlier caveats)

Yes it will as long as its an ACCDB and any APIs are suitably converted @GPGeorge You're right. My earlier comment about importing into MDB files was too broad. However, there are definite limitations. For example, although you can import tables from an ACCDB, you cannot link to them! I'm also...

EDITED to correct some over generalised comments: You may not be able to import all objects from an ACCDB to an MDB because the older file version has no knowledge of the newer ACCDB file format features. You also cannot link to tables in an ACCDB file or use an ACCDB file as a library...

@Levi_79 You could use my free app to do that https://isladogs.co.uk/extended-file-properties/