Database Issue Checker software

[jwhite]

You could do it temporarily, I suppose. The option is under Windows Features - type that to find the match and click it. I don't recall what that looks like in Win7.

[Lou_Reed]

https://answers.microsoft.com/en-us/...0-5c67be605c41

No matter what I have tried the VBA inspector setup wizard ends prematurely

is the message that I got. The link at the top of this post shows how to modify Windows 8 to allow VBA Inspector to install, but I have Windows 10 Pro. How is that changed for users of Windows 10?

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[jwhite]

It's the same in Windows 10. In the Cortana question box, type Windows Features, then select Turn Windows Features On or Off. Or go to the Control Panel and in left panel click "Turn Windows features on or off". The top selection should be .net f 3.5. Click in the box so the black-fill goes away.

[Lou_Reed]

Okay, by doing this even temporarily what is my risk? The software has to be there for some reason, so what is the risk of turning it off?

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[jwhite]

The only risk is if you have another installed application that requires it and when you try to run that application, it will error out and tell you it needs it - no harm to your computer at all. Disable it, test the install again, then enable it back. Or leave it disabled and then later you may find out the app that requires it.

[Lou_Reed]

Okay, just satisfy my curiosity. What does it do?

R,

Lou Reed

[jwhite]

Google can be your friend: https://msdn.microsoft.com/en-us/lib...v=vs.110).aspx

[Lou_Reed]

Okay, I was finally able to get .NET Frameworks in all of its versions uninstalled on my version of Windows 10 64 bit, Pro. I was still not able to the
get VBA code inspector to install. Thus this fact of .NET Frameworks installed or not is not relevant to the reason the install wizard of the VBA code inspector
ends prematurely. It is just not important.

The frustrating fact about this, is that when the install fails or ends prematurely, it gives no reason. Thus I have no way of knowing why the install crashed.

Is there some kind of Windows 10 Pro log that might contain the progression and designate when the install fails and why?

That would be a big help if it did.

Any help appreciated. Thanks in advance.

Respectfully,

LouReed

[jwhite]

I recommended earlier that you contact the author of the app with the issue - recommendation still stands.

http://www.team-moeller.de/en/?Add-Ins:TM_VBA-Inspector. Go to his About page to click link to email him.

[Lou_Reed]

I turned off the Subdatasheet option in my MS Access 2010 db. This is supposed to speed up the loading and operation of the db. I am now concerned that it may affect the db's operation.

I have many subforms in the db and I am afraid that it will cause problems when I try to open a form that has a subform attached.

Is this a problem. Should I turn it back on?

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[jwhite]

The main issues with subdatasheets are:

1) They lack the events that you get if you use a subform, such as
Form_BeforeUpdate. That means you cannot control what the user enters,
validate ranges, provide warnings, respond to Undos, and all of the things
that make Access forms so great.

2) They take time to load. In fact, where a form has several subforms, it
can slow the loading of the form by orders of magnitude, turning a zippy
piece of software into a real dog.

3) They are unreliable. If you accept the "Auto" default, you don't really
know which related data the user is going to get.

I have a created and maintain small to large databases, all with subdatasheets off with no adverse effects.