Search results

I am planing to distribute via CD-ROM a demo version of my Access 2010 pawnshop management app to select pawnbrokers in a geographic area. I was thinking about combining the frontend objects and backend tables into a compiled password-encrypted accde, and using 2010's packaging wizard to sign...

Perhaps it could also be the infamous version 1803 / Win10 MS bug, or his D path is not a trusted location?

Hi Dave, I noticed you tried opening them from your D drive, maybe it needs to be on C? Also, are you opening it in exclusive or shared mode from the cmd shell command line?

AFAIK, the only portable database that I know of that doesn't require user installation is a devices' native filesystem.

Hi @Pat Hartman , Hope you are well. Its been a while since we last connected. As this thread stands, unless the OP provides more clarity, I think the point of this thread is moot because his initial statement is controversial. I bid 3NT on this thread :) @The_Doc_Man Thanks for the heads up...

It's possible to store all those as BLOB's within a free db server with no limits like PostgreSQL but it requires installing PostgreSQL software in order to access those objects. NOTE: When I include a weblink in my posts and press "Save", an error message says it looks like you are posting...

Why not store the images externally in OS folder(s) and the path for each image in an Access table? This way your images can easily be ported and you don't have to worry about db size limits and performance degradation.

Hi Doc, I guess Colin needs to go back to the drawing board and improve the hardening of his frontend demo because as you are well aware that while the frontend has an open link to backend tables, if you enable the various FE UI features, options, and view string values with the vba object...

The multiple security-holes in compiled accde front ends were the low hanging fruit I was able to exploit to unlock enough options which made it possible for me to use, e.g. the vba object browser to view values like RC4_Key, your Cipher key, strPassword, the password to your encrypted backend...

I am not an experienced Access/VBA developer and after not too much effort I was able to break into the accde frontend of the "encrypted-split-no-strings-demo-database" security challenge, alter settings, and view enough things which made it possible for me to reach RC4 encrypted data in the...