Migrate to SQL

Posted on 2014-02-13
Last Modified: 2014-02-13

This is a follow up to a similar question

1. If migrating to SQL then all the forms, reports, modules, queries, relationships will be lost?  Meaning they do not convert over and will need to be rebuilt in SQL?  

2. To me, "migrate" means everything moves over and if not, then the tables are only a very small part of the big picture and I dont see a lot of time being saved with any migration to SQL from Access.  You basically have to start over is how I see it.

3. Wouldnt the programmers need to spend a lot of time developing the interface?  Meaning that if the IT dept says "yeah well put someone on it" but in reality they dont plan to spend much time developing it then its probably fair to say the interface will not be well done and getting bugs fixed etc etc will be like pulliing teeth.   My pt is that the developer can not approach the job carelessly and needs to devote many hours even after the initial interface.

4. If the tables are in SQL then its common to build the interface in SQL as well?  

Thank you for the help...
Question by:pdvsa
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
LVL 61

Expert Comment

ID: 39856497
1. If migrating to SQL then all the forms, reports, modules, queries, relationships will be lost?  Meaning they do not convert over and will need to be rebuilt in SQL?  

Not quite...

SQL Server holds your data.  Just think of it as a new back-end.

Your Front End (Access) links to the SQL Tables.... with very little change needed to your form/report/query interface.

There are a few things needed - one that comes to mind is that all of your recordset and action query code will need the dbSeeChanges option added.  

But for the most part, your FE will remain the same.

Author Comment

ID: 39856517
Oh I see what you are saying.  
I failed to mention that IT does not want to use Access at all.  

does this change something?
LVL 61

Accepted Solution

mbizup earned 500 total points
ID: 39856571
<< does this change something? >>

Changes everything.

I would double/triple check... that they are not allowing Access even as a user interface.

If it is allowed, changing to a SQL Back-end is very smooth.

If they are absolutely positively not allowing it, then the changes will be significant, including:

1.  A complete redesign and rewrite of ALL of your forms, reports, code and queries.

2.  The learning curve involved in adjusting to a totally different platform such as .Net for the user interface.
Online Training Solution

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.


Author Comment

ID: 39856579
I was under the assumption that SQL is also a FE.  

What other FE's are there?   .NET is one I can think of.

If we use a different FE other than Access then we are are completely at the mercy of IT is how I see it.  I dont want that as it will take too much time to wait on them.

Author Comment

ID: 39856583
(did not see your previous post)
LVL 61

Expert Comment

ID: 39856585
4. If the tables are in SQL then its common to build the interface in SQL as well?  

SQL is really just the data, and maybe queries/stored procedures to manipulate it to some degree.

It is NOT a user interface.  That is where Access ideally comes back into play, or if that is totally out of the question it would be .Net or something else.

Possible the easiest to transition to if necessary would be VB.Net (but it would not be a straight-forward copy/paste or import, it would be a redesign/rewrite)


Missed your last posts too :)

Author Comment

ID: 39856614
I am sure they dont want to use Access.  They manipulated IT into saying Access is not an approved software.  It makes no sense because we were already using Access.  What I am dealing with is someone that is above me and is extremely inefficient at what they do and desires to have their name as "author" on something.

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

I see at least one EE question a week that pertains to using temporary tables in MS Access.  But surprisingly, I was unable to find a single article devoted solely to this topic. I don’t intend to describe all of the uses of temporary tables in t…
This article describes a method of delivering Word templates for use in merging Access data to Word documents, that requires no computer knowledge on the part of the recipient -- the templates are saved in table fields, and are extracted and install…
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question