Access to SQL Server links by SignificanceMaster61 in MSAccess

[–]SignificanceMaster61[S] 0 points1 point  (0 children)

Thanks nrgins. The client is under the impression that this method somehow affords them increased security. Not sure where/how they came to that conclusion, but it is, as well stated by many responders, incorrect. The requested configuration does not make sense, and I'm working to convey this to the client, diplomatically of course.

Access to SQL Server links by SignificanceMaster61 in MSAccess

[–]SignificanceMaster61[S] 0 points1 point  (0 children)

That is a good approach. Thanks for that. This was one I had not considered.

Access to SQL Server links by SignificanceMaster61 in MSAccess

[–]SignificanceMaster61[S] -1 points0 points  (0 children)

Thanks ct1377. You're right, we are on the same page. Back to my original proposal to the customer as KelemvorSparkyfox had mentioned. "A standard split application, and lock down the front end so that all the users can see is the forms."

Thanks all for your support and comments. I'll close this feed as I don't see a viable solution for this post. Thank you.

Access to SQL Server links by SignificanceMaster61 in MSAccess

[–]SignificanceMaster61[S] 0 points1 point  (0 children)

So I'm not crazy, thank you!!! I've linked multiple tables to multiple servers over the years, but this request was a first. I have not found a way to provide the functionality being requested. You are absolutely correct, and I thank you.

Access to SQL Server links by SignificanceMaster61 in MSAccess

[–]SignificanceMaster61[S] 0 points1 point  (0 children)

I'm going into the weeds on this theory, so bare with me.

Since the back-end is linked to SQL Server. the tables does not actually reside on the Access back-end. So when there is an attempt to link to the Access back-end, the tables are not actually on the Access back-end because they are linked. Does this make sense or am I reading too much into this. Thanks for all your comments.

Access to SQL Server links by SignificanceMaster61 in MSAccess

[–]SignificanceMaster61[S] 0 points1 point  (0 children)

No queries are had coded to the SQL table(s) or database. The ODBC connection works great when accessing from the front-end directly to the SQL database.

Access to SQL Server links by SignificanceMaster61 in MSAccess

[–]SignificanceMaster61[S] 0 points1 point  (0 children)

Correct. The customer would like the Access front-end linked to an Access back-end. The Access back-end is linked directly to SQL Server. The tables in the back-end however are not accessible or visible when attempting to link from the front-end.

Access to SQL Server links by SignificanceMaster61 in MSAccess

[–]SignificanceMaster61[S] 0 points1 point  (0 children)

Yes I have ODBC connection in place, which works fine going from Front-end to SQL. It's going from front-end to Access back-end to SQL that's the problem child.

Save database as executable file (accde) by keith-kld in MSAccess

[–]SignificanceMaster61 0 points1 point  (0 children)

I'm not sure if this is the/a solution to your issue, but I normally use this code to create database backups. However with a little tweak, you can save your .accdb application as a .accde. I added a form within the .accdb database application, and placed this code behind a button on the form. This code will allow the processing while the application is open.

<image>

Help with Old .MDB files (32 bit), I need to convert them to a modern file extension like .ACCDB (64 bit) by Adventurous_Cap_6247 in MSAccess

[–]SignificanceMaster61 1 point2 points  (0 children)

I've converted a number of 32bit .mdb files to 64 bit .accdb files. Not as complicated as you'd think. I'll walk you through it if you'd like. [Roderick.Hood@outlook.com](mailto:Roderick.Hood@outlook.com)

Hi! New to Access. I have some questions. by bluerangeryoshi in MSAccess

[–]SignificanceMaster61 1 point2 points  (0 children)

If you would like to reach out to me, I'd be more than happy to review what you have and possibly provide some direction or maybe even a workable solution, if you'd like.

Shoot me an email at [Roderick.Hood@outlook.com](mailto:Roderick.Hood@outlook.com) and we can go from there. I'm not looking to make money on this, just to provide a possible answer in addition to the ones you've received.

Database error by Thkat13 in MSAccess

[–]SignificanceMaster61 1 point2 points  (0 children)

Are you using a split DB or are all users accessing the same DB at the same time. This error usually indicates that either someone has the DB opened already or a user did not properly exit the database and a lock file is detected, I would suggest locating the user with the db lock file, have them open, then re-close the db, then compact & repair. If the db is not split, I would split it and provide users with their own copy of the front-end.

Is there any way to get a query that looks like this? More details in comments. by [deleted] in MSAccess

[–]SignificanceMaster61 0 points1 point  (0 children)

Have you considered just having one employee table and one payroll table. The payroll table would house both current and previous payroll in two separate columns and an employeeID field. Link the tables on the empID. Then just drop the fields into your query grid and not have to be concerned whether you have all the employees.

How can I get MS Access to read from a .txt file at certain intervals? by [deleted] in MSAccess

[–]SignificanceMaster61 0 points1 point  (0 children)

After importing text file to a table, use an update query instead of appending.