<div>
Hi Jim and Anders,<br />
Thanks for fast reply.<br />
<br />
-SQL server 2012 is on network (Windows 2012 Virtual machine)<br />
-I setup with login sa/password<br />
-Since my workstation (on same WAN) can connect, I assume port 1433 is open<br />
-When I setup with SSMA, it does not require a password, and work on my station. &nbsp;Do I need to not have SSMA create links, and just connect via file DSN?<br />
<br />
Thanks, Larry
</div>


<div>
You need to either create the same DSN you used on your PC on all the other PCs or you need to write code to make a DSNless connection.
</div>


<div>
Pat - would that be a connection using IP address rather than the server name?<br />
-Larry
</div>


<div>
The I.T. consultant installed SQL on the I;\ drive (data drive) instead of on the server's C:\ drive.<br />
I:\ drive has only folder called &quot;program files&quot;, in which is found Microsoft SQL server.<br />
Shouldn't SQL have been installed on server's C:\ drive?<br />
<br />
On my office server, I installed on C:\drive and I can connect to SQL server via its IP address (not via server name).<br />
Is this the issue?<br />
<br />
I do not know how to setup DSNless.<br />
<br />
Hope this enlightens.<br />
<br />
Thanks much, Larry
</div>


<div>
Yeah &nbsp;sorry ... SQL Server setup is out of my league, and I'm a bit late to the SQL Server party (but I learn FAST). Our IT Dept sets up all SQL Server db. We have one for our group, with full admin rights. Currently, we have a Front End that my database loader copies from a share drive to user's local workstation, and the tables (~10) are linked (FAST) 'DSNless' on the fly - which is &nbsp;just a few lines of VBA code - easily found on the internet. &nbsp;It uses Windows Authentication (I think that is the correct term), which does not require any hard coded UserName or Password. Only needs the SQL Server Name, SQL Server Database Name, remote and local table (if different) Names in the Connection String ... and a couple of other parameters - which I think tells it to use Window Auth.<br />
Approx 150-200 users connect daily with no issue.
</div>


<div>
Connections to the SQL server can come in several flavours. I don't really know how it looks when SSMS has set it up for you. You can mouseover a linked table to the the connection string, or to get it in a more copy/paste friendly format try the following code from your accesss frontent, in the Immediate Pane<br />
? Currentdb.Tabledefs(&quot;Inser<wbr />tNameOfLin<wbr />kedTable&quot;)<wbr />.Connect<br />
This should return the connect string to your immediate Pane.<br />
<br />
Then paste the connect string here, and we can likely proceed from there.
</div>


<div>
Experts,<br />
Thanks to everyone. &nbsp;The issue (suggested by Anders) was adding users and permissions. &nbsp;When I created Db, it automatically assigned me as a user/admin and gave privileges. &nbsp;So solution was to manually add the other users on Domain, and give certain privileges.<br />
<br />
Thanks to everyone!<br />
Blessings, Larry
</div>


<div>
Your welcome. Sometimes I have actually taken the approach of creating a SQL server login account with username and password and use that for Admin stuff, and leave my AD account as a &quot;regular user&quot;. This also makes it easier to test, because I will break if I don't have the permissions. In essence I make sure that my AD account has the same permissions as any users who are going to use it.
</div>


<div>
Thank You Anders for useful followup advice. <br />
Your help greatly appreciated.<br />
God Bless, Larry
</div>


<div>
<div class="content wysiwyg-content">
Hi Experts,<br />
I have successfully moved Access back-end tables to SQL server 2012, using SSMA for Access.<br />
I can place the front-end (with all the links to SQL) &nbsp;on either my C:\ drive or on the server and it work.<br />
<br />
But no other computer on same LAN can attach. &nbsp;They get an ODBC connection error.<br />
I've tried having SSMA create links, and have manually created machine and file ODBC links.<br />
<br />
Any ideas appreciated.<br />
<br />
Thanks, Larry
</div>
</div>


Hi Experts,
I have successfully moved Access back-end tables to SQL server 2012, using SSMA for Access.
I can place the front-end (with all the links to SQL)  on either my C:\ drive or on the server and it work.

But no other computer on same LAN can attach.  They get an ODBC connection error.
I've tried having SSMA create links, and have manually created machine and file ODBC links.

Any ideas appreciated.

Thanks, Larry

Access with Sqlserver database with Access front end is on network drive

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.

Microsoft Access

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.