?
Solved

Migrate to SQL

Posted on 2014-02-13
7
Medium Priority
?
212 Views
Last Modified: 2014-02-13
Experts,

This is a follow up to a similar question
http://www.experts-exchange.com/Microsoft/Development/MS_Access/Q_28352469.html

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...
0
Comment
Question by:pdvsa
[X]
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
7 Comments
 
LVL 61

Expert Comment

by:mbizup
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.
0
 

Author Comment

by:pdvsa
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?
0
 
LVL 61

Accepted Solution

by:
mbizup earned 2000 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.
0
Independent Software Vendors: 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!

 

Author Comment

by:pdvsa
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.
0
 

Author Comment

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

Expert Comment

by:mbizup
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)


EDIT:

Missed your last posts too :)
0
 

Author Comment

by:pdvsa
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.
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

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

Access custom database properties are useful for storing miscellaneous bits of information in a format that persists through database closing and reopening.  This article shows how to create and use them.
Access developers frequently have requirements to interact with Excel (import from or output to) in their applications.  You might be able to accomplish this with the TransferSpreadsheet and OutputTo methods, but in this series of articles I will di…
Basics of query design. Shows you how to construct a simple query by adding tables, perform joins, defining output columns, perform sorting, and apply criteria.
In Microsoft Access, when working with VBA, learn some techniques for writing readable and easily maintained code.
Suggested Courses

765 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