Search results

This is what I'm leaning towards: Although I like: Thanks all

Further info: I created the field in an existing table. It appears Access sets the existing row values for the field to 0, even though I specified a default of Null. So I have to go and set all the values to Null to get that default?

Please explain: 0 would be No, no?

As I said, they have to make choice. The default should be Null (they haven't made a choice yet).

I'm creating a new Yes/No/Null field in a table. Null means unchosen. When the user leaves the form that has the field, they have to make a choice of Yes or No. What's the proper way to set this up? I don't think I want a rule in the table as I want to handle that in the form. Here's my...

I know about that, I was was wondering if there might be a way to do it in code. I'm particularly interested in links. So if someone links to the db, a way to detect that even if they don't open the linked table.

Does anyone know a way to detect whether an incoming connection is made to an Access db, or if a someone links to it? Thanks

I agree that it's a good price for all it does, and FMS has a nice licensing model. In my case it's not about cost but the approved software acquisition channels my company uses. I've recommended other FMS products to them but so far no dice.

I would love to have that but my boss won't go for it (so far).

I agree but until users I'm supporting uninstall the older version, I have to support them with what they have.

That's just what I've found. You would think that Open With and version specific shortcuts would work, but in some cases, no :(

Thanks, I'll check it out.

I know, it's a tough crowd. Some of them may be still running 2003. I uninstalled 2010 on my dev box just because of the headaches, but now I'm reinstalling it to test different scenarios.

I'll need to account for if the user has 2010 and 2016 open at the same time. Thanks, that gives me a starting point.

Sounds like the best approach for now. If you have a sample script, please forward. Thanks

I agree. Now if I can get the client to agree .. In the mean time, a solution other than opening Access first and then pointing to the file, would be welcome.

Been there done that - see above. It doesn't always work.

I have and it doesn't always work. On machines that experience this, the only sure way I've found is to open the correct version of Access first, then open the file from there.

I'm running into the problem of opening accdb's in the wrong version of Access on user's machines. This seems to happen most with machines that have both 2010 and 2016/365 installed. Anyone have a decent workaround to that, like a script or batch file? Even a hardcoded shortcut such as...

Same issue I had: an office add-in isn't active and loaded until you manually load it (by clicking it in the add-in tab). I wish there were a way to load it automatically but it seems like that would require a COM wrapper.