Thanks for sending the youtube video. I have already correctly linked to the sql server on the server computer, and it runs smoothly as well. My problem is when lunching the front end in other computers, it won't work. Any solution for this? Thanks.
Bet Regards,
Kevin
hi Kevin,
You're welcome. Each computer needs to be set up to connect to SQL Server. Here is a video tutorial that may be helpful:
How to Configure ODBC to Access a Microsoft SQL Server
https://www.youtube.com/watch?v=tUiaK5fRH7k
~crystal
Dear Crystal,
Thanks a lot for your reply. Would you please explain a little bit on how other computers are initially set up manually?
Best Regards,
Kevin
?????? WPS?????????????????? "crystal [MS_Access_Professionals]" <MS_Access_Professionals@yahoogroups.com>???2019???4???27??? 21:41?????????
??
hi Kevin,
when you use a DSN file to link, it is just like you filled out the
information in the dialog boxes yourself. The DSN file is not stored in
the connection string. Advantage of having it on the network is that you
don't have to take it with you.
Other computers may need to be initially set up manually so they have
the driver. Also each user needs credentials, depending on how users are
set up for the back end.
~crystal
On 27/04/2019 04:24, Qingqing??
[MS_Access_Professionals] wrote:
> Dear All,
> I have created a file DSN, and put it in a shared folder. After linking MS Access application with SQL Server via this DSN, everything was fine. Then I disposed the front end to other computers within the same network. Then the front end won't connect to SQL Server. By the way, there's no sql server installed in the front end computers. Anything wrong with my approach? Thanks in advance.
> Best Regards,
> Kevin
>
Posted by: Qingqing <qingqinga@yahoo.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (6) |
Tidak ada komentar:
Posting Komentar