Solved

Migrate to SQL

Posted on 2014-02-13
7
197 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
  • 4
  • 3
7 Comments
 
LVL 61

Expert Comment

by:mbizup
Comment Utility
<<
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
Comment Utility
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 500 total points
Comment Utility
<< 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
How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

 

Author Comment

by:pdvsa
Comment Utility
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
Comment Utility
(did not see your previous post)
0
 
LVL 61

Expert Comment

by:mbizup
Comment Utility
<<
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
Comment Utility
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

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

When you are entering numbers in a speadsheet, and don't remember what 6×7 is, you just type “=6*7" instead. It works in every cell! This is not so in Access. To enter the elusive 42 in a text box, you have to find a calculator, and then copy the re…
QuickBooks® has a great invoice interface that we were happy with for a while but that changed in 2001 through no fault of Intuit®. Our industry's unit names are dictated by RUS: the Rural Utilities Services division of USDA. Contracts contain un…
Learn how to number pages in an Access report over each group. Activate two pass printing by referencing the pages property: Add code to the Page Footers OnFormat event to capture the pages as there occur for each group. Use the pages property to …
Using Microsoft Access, learn some simple rules for how to construct tables in a relational database. Split up all multi-value fields into single values: Split up fields that belong to other things into separate tables: Make sure that all record…

744 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

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now