Search results

Greetings to the well of knowledge... I have an Access front-end that talks to an SQL Server 2008R2 back-end (yes, I know I need to upgrade this). This front-end is used by users on a Server 2008R2 remote desktop server. I am in the process of completing the build-out of a new Server 2012R2...

And we have a BINGO!

Greetings to the well of knowledge... I am sure most if not all of you have been touched by the recent rash of defective MS updates for Office. :banghead: Despite my best efforts to remove the bad patch(es) or apply the alleged fixes, I continue to have problems where my applications just...

Thanks to all of your for insight and assistance. I learned an awful lot today thanks to you.

We are just starting our Windows 10 rollout. What I'm going to try is modifying the trust settings on my Win10 "gold" image so that everything is set when I image a PC.

Most of my databases do a lot of initialization during Form_Load. I wonder if this is where the trust error is happening.

So I changed the trust center settings to accept VBA and Active X. This now makes the DB start properly. Is this applied at the DB level so that anyone who copies the DB will get the same settings?

As I noted, I don't allow users to run the copy on the network shared. I require them to take a copy to their desktops.

That makes sense but when running under Win10 and using Access 2016 runtime, the warning doesn't come up. Access Runtime just starts then closes with no warnings or errors. Interestingly, on Win7 PCs running Access 2016 runtime, the warning DOES appear.

Greetings to the well of knowledge... All of my Access DBs are front-ends that talk to our central SQL Server. I manage the development and release new versions on a fairly frequent basis. I install the "gold" copy of the Access DB on a network share and instruct my users to take a copy of...

NAILED IT! How did you know????

Greetings to the well of knowledge... I have an Access 2016 front-end talking to an SQL instance. Last week, some issues arose that required me to restore a couple of corrupted tables from backup. These tables restored successfully but since then, one of the tables appears to be in "read...

Yes. I noticed the typo. I changed all Me. references to Me!...these did not work.

Something amiss in Access 2016??? I just took the last good version of the DB and made the same changes to the DB using Access 2010 and no errors are being thrown, either in Access 2010 or Access 2016. This is weird.

Me! = No good.

I must also mention that these "Provider..." fields were just added to the DB using Access 2016. If I do this using Access 2010, no errors.

Unfortunately, I can't. It's all linked tables from an SQL Server DB. The Access piece is just a front end.

"The expression you entered has a field, control, or property name the <application> can't find."

Yes, all text boxes. The data is provided from an external web form source and fills the form so that it can be viewed (not edited). The "user" chooses" this from the web form and the data is written to the table from the web form. Basically, the form asks if the application is being filled...

I should also add that all of the other "Provider..." fields display as #Name? in the form.