Search results

Service accounts are not what users use. https://sql-articles.com/articles/general/sql-server-service-accounts/

As I said, I am not talking about service accounts. If the user doesn't actually ever know his password, then the hardware lock works but at a cost. I don't think I've ever had a client that used hardware locks for every computer.

I would use the AfterUpdate event to trigger the log. That way, you are certain that the change to the record was actually applied. If you create the log in the BeforeUpdate event, you may create log records for rows that were never actually updated. The tricky part is you no longer have the...

If the client wants to provide hardware keys that's fine but it doesn't solve the problem we were discussing.

Each user has an individual account but I pick the password so he doesn't know it. His windows login won't work. He logs into the Access app using whatever password he choose and the app logs into the server and links the tables using a password that only the DBA and I know. There are two...

But you said you do.

I think that is the wrong lesson to learn. I NEVER delete the table links if I intend to reuse them with updated workbooks and I've never, ever had this issue. Deleting the link will cause all of your querydefs that use the linked workbook to break if you C&R while the table is deleted. THAT...

I never said to use service accounts. No one ever asked me what I do, you all just poo-pooed the issue so I didn't bother.

I believe that @arnelgp created a class to do this. I don't have a link. I never downloaded or tested it because I would never implement this functionality this way. The simple, method is to use cascade delete. That way, when you delete the parent record all the child records are also...

I'm not sure who you are talking to. It can't be to me.

I never suggested using a single account. All users should have unique accounts. They just shouldn't know their credentials.

Then you can't build an application using bound forms.

If you are happy with that solution, who am I to argue. The limitation is that you MUST have the form open to the correct record when you run the report. This seems like it could easily be a point of failure.

Just because you trust them doesn't mean you need to leave gaping security holes that can easily be closed. Your Access FE probably locks the users out of design view on anything and doesn't give them options like - delete all tables? But are you willing to allow them to use their SQL Server...

What happens when you try to open the database? If you are having a security problem, you need to define new trusted locations.

Once you know your credentials, create a new, empty Access database and link to tables on the Server. Can you do it? You won't have the credentials to manipulate objects but you can update data because that is what you need to allow the Access app to function.

It is the striving that gives us purpose and makes us grow. But I agree - way too many are internally motivated to play God rather than to learn and grow. We have gotten to the point where we know enough about genetics to accidentally destroy ourselves and the planet.

Because, using Windows Authentication allows knowledgeable users to get directly into SQL Server without using your Access application. If you're OK with that, then you have a very large security hole that I hope will never bite you.

No, if you change the way you link, you get an error when the file is MIA.

or better yet, in the query so you only do them once and it fills the form and the report.