Thanks so much for the additional information, Bill!
I will spend time to learn SQL Server Migration. It seems to be a much better approach.
Regards,
Tim
--- In MS_Access_Professionals@yahoogroups.com, "Bill Mosca" <wrmosca@...> wrote:
>
> Tim
>
> I use SQL Server databases as my applications' back ends all the time. When you start out dong this you will find you have more control over the data. And Access's JET/ACE works's just fine. As you gain more knowledge about SQLS you will learn when it is best to use pass-through queries, but I rarely use them. A well-designed application usually does not require pt queries (IMHO).
>
> Design your tables in Access. Then use the SQL Server Migration Assistant (SSMA) for Access to upsize. You can download it for free at:
> http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=28763
>
> You will be required to register it using your MS Live ID. If you don't already have one it is a good idea to get one. You can take advantage of free storage on SkyDrive, hotmail account, etc.
>
> SSMA does an excellent job of converting the tables. It will convert queries into views should you desire. You should also read my article on the quirks of using SQLS as a back end.
>
> Bill
>
>
> --- In MS_Access_Professionals@yahoogroups.com, "timdbui" <timdbui@> wrote:
> >
> > Hi Bill,
> >
> > Thanks so much for your wise advice! Yes, I should use the lowest denominator to insure compatibility. It makes a lot of sense.
> >
> > I really have no plan to use Access with the web. The only reason I am thinking about Access 2013 is its using SQL Server as the engine rather than JET. I kept thinking, rather than starting to learn SQL Server to make it as the engine and using Access 2010 as the front end for quick development, maybe Access 2013 is my answer. But not knowing enough about this subject, I need advice from more knowledgeable people.
> >
> > Thanks again for your help!
> >
> > Regards,
> >
> >
> >
> > --- In MS_Access_Professionals@yahoogroups.com, "Bill Mosca" <wrmosca@> wrote:
> > >
> > > Tim
> > >
> > > I know many Access users want the latest and greatest, but is there really a need to go to 2013? Are you going to develop a web application? That would be the only reason I can see to upgrade at this point.
> > >
> > > As far as I know Access 2010 cannot link to tables in 2013. However, you could leave the tables in 2010. But being the only one that does development why would you not use the version that the others use? When I was a contractor I had several versions of Access available to me so I could develop in the lowest denominator so I was sure that all my clients for a contract could run my applications. Not doing so is asking for trouble.
> > >
> > > I suggest if you want to get used to 2013 do personal projects, but develop in your clients' environment for applications they will be using.
> > >
> > > Regards,
> > > Bill Mosca, Founder - MS_Access_Professionals
> > > http://www.thatlldoit.com
> > > Microsoft Office Access MVP
> > > https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-64270730881E
> > > My nothing-to-do-with-Access blog
> > > http://wrmosca.wordpress.com
> > >
> > >
> > >
> > > --- In MS_Access_Professionals@yahoogroups.com, "timdbui" <timdbui@> wrote:
> > > >
> > > > Hi, would anyone of you please advise me on this issue:
> > > > Our group consists of 4 Access 2010 users, and I am the one who does the development and administration. I slit our database into front end and back end. I am thinking about upgrading to Access 2013. My question is can I be the only one in the group who uses Access 2013 and have other users (who will use Access 2010) to link to the backend that I created via Access 2013?
> > > >
> > > > Thanks so much for your help!
> > > >
> > > > Regards,
> > > >
> > > > Tim
> > > >
> > >
> >
>
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (5) |
Tidak ada komentar:
Posting Komentar