Stub method is giving me issues (1 Viewer)

[MajP]

I am with Pat, this is such an overly engineered approach to do a trivial task in Access. If you did it using Access and not working around it.
If you want to go this route and you are experienced in .net then you are much better off building it in .net as the front end and using either your access db as the back end or migrating to sql server. You have more direct control if you go with a .net FE.
Since it runs on access it will run on a free version of SQL. Either go that route or stop what you are doing and do it like everyone else would do in Access. But this whole moving to a dictionary is silly, IMO.

 

[Pat Hartman]

and I did consult with the AI about some things like using the .Tag line to pass metadata and that the PK isn't assigned to a stub until the .Update event and that I needed to use DAO to make access play nice,

That information is incorrect. Very much of the info regarding how Access works is simply made up based on the AI understanding of how other apps do the same thing.

When the BE is Jet/ACE the autonumber PK is assigned immediately as soon as you dirty the record (type one single character in any control). You would see this on any form where the PK is visible. When the BE is SQL Server or other RDBMS, the PK is not assigned by Access and so is not generated until you try to save the record at which time Access sends the append query to the server. The server then returns the identity column which will show in the PK control if it is visible. In the case of Jet/ACE, the autonumber is burned and leaves a gap if you don't actually end up saving the record. This disturbs people because they have a hard time understanding the purpose of the autonumber and don't like seeing gaps.

Only your AI thinks that you need DAO to make Access "behave". No actual Access developer would share that opinion. Part of your dislike for Access is the misinformation you are getting from whatever AI you are using. @Uncle Gizmo is our most AI conversant expert and he is working with several. Perhaps he will chime in and suggest which of the AI's he uses has the best actual knowledge of Access and VBA.

The best feature of Access is bound forms. That's what saves you tons of work once you understand how you should work with them. You are banging your head on a wall as you fight with Access. Either stop using Access and recode the app using a platform you are familiar with as MajP suggested or learn how to use Access so you can stop billing your client for so much unnecessary work. You can still use the badly designed ACE BE if you don't know how to fix that.

If you want to protect the client data, run some update queries to scramble it. We prefer that anyway. Someone has posted a tool I believe but I can't remember who. It might have been @MajP.

 

[MajP]

Not me, but here.

Scramble Text

This function replaces every character with a random similar character. I use this function to anonymize data in tables. Almost but not quite entirely unlike the post made by Micron a few months ago. Share & Enjoy! Option Compare Binary Option Explicit Public Function ScrambleIt(strString...

www.access-programmers.co.uk

 

[Pat Hartman]

Thanks Pete