My limited knowledge 2 cents worth,
So I have been recently learning SQL and have a personal task and project database that I use for work. I have been researching how to convert my database to SQL as a FE/BE. I have created tables in sql and did an odbc link to access and have come up against some minor difficulties with the whole process. My research has taken me from everyone saying that databases should be split, to there are performance issues and other problems with this scenario. I want to learn but I am frustrated with the ability to discern what is personal preferences or personal objectivity with the subject. even your web page has an article about linking tables that have hidden gotchas.
I will continue to have a goal to eventually get a working environment with my database and sql. I just do not know if it will ever be a production database or not because of my limited skill set with sql. I would need to access it with teamviewer to a computer I have at home so it is always accessible. I cannot afford Azure so that is not an option right now.
Jim Wagner
On Monday, June 1, 2015 7:44 AM, "wrmosca@comcast.net [MS_Access_Professionals]" <MS_Access_Professionals@yahoogroups.com> wrote:
Adam
I'd go with SQL Server with an Access FE. (Read my article on using SQL "Working with SQL Server Linked Tables: The Hidden Gotchas" http://www.thatlldoit.com/Pages/howtosarticles.aspx
If the users have access to the SQL Servers the FE could probably be pushed out from that server. I wouldn't go with SharePoint simply because any Access DB that uses it is very limited.
Regards,
Bill Mosca, Founder - MS_Access_Professionals
http://www.thatlldoit.com
Microsoft Office Access MVP
http://mvp.microsoft.com/en-us/mvp/Bill%20Mosca-35852
My nothing-to-do-with-Access blog
http://wrmosca.wordpress.com
__._,_.___
Posted by: Jim Wagner <luvmymelody@yahoo.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (3) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar