Search results

I didn't know the order --- probably because I tended to use one OR the other. Very good to know that.

Funny you should pick the "StartUpShowDBWindow" example, as I'm thinking of adding that one to my list since I have that checked once in a while.

@isladogs - I have a tiny follow-up question, if that is OK. On the db.CreateProperty line, there is the "dbText" argument. Intellisense is telling me that it is the "Type". I'm thinking it must mean the type of the property name, not the type of the property itself (as that appears to be an...

Wow - Awesome. I think NOW I can see so much more of the reasoning for what seemed surprising to me (in my little Access world -- ha...) Very cool - and thank you very much.

I'm not sure if it affects this - but we USED to be able to manage trusted locations... but no longer... Maybe the AutoExec macro will still work regardless. (I seem to recall opening one of my old Access files recently where I had included an AutoExec macro and it tried to run it. I don't...

This is one of those things that I just sort of muddle through, but also have wondered why it feels inconsistent. Is there an obvious answer to: Why is it that you need not use myDB.Properties("Name") but you must use .Properties in the other case?

Hmmmmmmm. I did not know this. This sounds like one of those things that I may have heard about once, it sounded intriguing, but then I never tried it out - and then forgot it. Interesting though.

Indeed. And I have used that approach before, but I vaguely recall running into problems at some point in our environment as the security posture has continued to tighten. I recall running into some friction with use of the AutoExec macro due to IT policy changes. I'll look back into that to see...

OK - Interesting. I'm not certain if I was doing that searching in a DB that had a startup form already set - but I thought it did. (It may be more likely I simply missed it.) But - as long as I can find one that IS there via VBA, and can set it, if needed, then that works out great. It is just...

Right - "Default" is not enough... Sorry 'bout that... So I'm talking about this:

OK - wild. I thought I looked through every property of the database object. I probably looked for "DefaultForm" - so missed the "StartupForm". I'll take a look at this --- thanks!

Correct... in Options where you tell it what form to start with. (I figured this meant it would be in Application.SetOptions - but I've had trouble finding a solid list of exactly what arguments are allowed with that.

I would like to be able to read/write the default form that is set in MS Access. I've tried looking in the usual places like CurrentdB., Application.SetOption, CurrentProject., but can't seem to find it anywhere. I've even tried peeking into the MSys tables, and it seems to be well hidden. Is...

Excellent! Yes - thank you ---- will do!

OK - So, it looks like it was nothing more than me accidentally closing out the relation too early by appending it before visiting the next set of fields. Due to this, it was no longer available to add more fields to. Ugh. I would add though, that in MS parlance, the "relation" is a table...

Here is the 'original' screenshot of the relationships, and then the one after trying to reconstruct from saved data... I thought I'd try to simplify and highlight the problem areas... probably not needed, but... One other thing I'm pondering. I saw (somewhere) that the 'name' for the...

I'm noticing that the code that exports this information does indeed loop through multiple 'fields' for a given 'relation'. So, it seems to be able to read them out, but for some reason, trying to write multiples back is fussing at me.

So, I'm trying to do exactly the same thing as this post... https://www.access-programmers.co.uk/forums/threads/trying-to-replicate-relations-from-an-external-database.86740/post-387504 I'm trying to create relationships in an external database, based on data I've previously saved in a file...

I will take a look at that - thanks! I do wonder how that code segment exists, with tables in it, if it is known to not work with tables. But - again - no worries. Just happy to have turned the corner on this and hopefully the mostly-difficult stuff is behind now! thanks again!

Very interesting! Sounds like you are using these concepts both inside and outside of MS Access? Regardless, using data to drive UIs is something I've seen, and used minimally, but yes - very powerful!