Q. When I tried converting a database using the upsizing Wizard it failed to convert all my data, hope can you help with this?
A. MUST automatically validates the date time fields and required fields, listing and correcting bad data, removing any obstacles to converting your data. Included in this is software to transfer data from large tables in blocks which reduces the likelihood of network timeouts.
Q. After I have upsized my database, how can I move to a live system without repeating all the upsizing steps and adding all my new design work in yet another SQL Server database?
A. MUST will automatically remove the database validation and constraints, drop the indexing, empty the tables, then migrate the latest data, add back in the relationships and constraints and put back the indexing for you.
Q. How do I find out what the upsizing systems is doing as I want to be able to make very subtle changes during the migration?
A. MUST not only directly upsizes into SQL Server, but can also generate SQL Server script files to do the upsizing, you then get a script which creates all your tables, constraints, indexing and can even import the data directly into SQL Server.
Q. We have three Access databases, can we put them into one SQL Server database?
A. You can upsize as many databases as you like into a single SQL Server database, but MUST also supports schemas which split your database inside a single SQL Server database, schemas can work like having several folders inside one database. The use of schemas becomes essential in bigger applications. MUST can also split a single database up over multiple schemas. One further point is security can be simply managed using schemas, MUST will create your database roles and you have a simple interface for planning the permissions on your schemas.
Q. I have over 500 queries which I want to convert to views and stored procedures, other tools only seem to convert a very small number of the queries, they fail for any queries containing references to controls like Forms!Order!txtOrderId, what can I do ?
A. MUST+SQL not only converts on average over 86% of your queries, but it also automatically identifies all screen controls, and creates a special parameter table to replace them, in addition it modifies all the SQL to give a seamless transition to getting the queries to work in SQL Server.
Q. I have queries which have calculated fields referring to other calculated fields is this going to be a problem?
A. Well SQL Server will not allow this, but MUST will automatically re-write your SQL using a technique called nested SQL which will allow your queries to continue working.
Q. I have two Access tables with a relationship, I inherited this system and one side of the relationship is a text 10 field, and the other a text 15 field. Will this be a problem?
A. SQL Server will not be happy with that, it will demand that you make both fields the same. Thankfully MUST automatically detects this and allows you to select which size of field to use before completing the upsizing.
Q. I have a lot of queries which use my own special VBA function, why won’t they upsize?
A. They will with MUST+SQL, the product automatically identifies any custom VBA functions and it generates a SQL Server function to replace your VBA function, you will need to then supply the body code for the functions after converting all your queries. The product also comes with a built in VBA support library for Access functions which do not simply translate into equivalent functions in SQL Server.
Q. I want to add some auditing to my upsized database, can you do this for me?
A. MUST can automatically add four fields to each table which track who and when records were created and last edited. This is great for showing on your Access forms, it can also create a mirror of your key tables in an auditing database if you want to track all your deletes and changes at a field level.
Q. Once I have upsized, can I ever take away an Access copy of the database design and data?
A. Although you can’t get everything back, MUST can reverse engineer a SQL Server database design and data back in Access. This can be useful when you still prototype with Access and want to use one of your existing SQL Server designs as a starting point.
Q. I downloaded you trial version of the software and was very impressed, but why did it not let me upsize the relationships?
A. Ah yes, we have to give you an incentive to buy our full product. The trial version has a few limitations built in, but we guarantee you will be able to do this in the full version.
Q. I have two machines that are used by me for development - one with Vista / Office 2007 and the other with Windows XP and Office 2003. I have SBS > 2003 R2 with SQL 2005 installed as my server. So, my question is this, can I use this product on both systems?
A. As long as the software is installed exclusively for your use, then you are allowed to install the software on more than one machine. You are also permitted to install the software temporarily on a clients machine for the purpose of performing an upsize, in this situation again the software is for your exclusive use. Thanks for the enquiry Jim and we hope you will have lots of success converting your systems.
Click here to read the MUST+Web FAQ page
Q. Are there any support forum or help documents to read through?)
Before downloading the software, please read the Terms and Conditions
Q. Hi Garry or Andy, I’m working for a client with a split front end/back end access 2007 database in .mdb format. We want to move it to a SQL backend for several reasons. I downloaded the trial version and used it to upsize the database, which worked brilliantly. I then detached the database and moved it on to the client’s server and went to use the MUST utility to relink it to their front-end, but it wouldn’t work. I believe I selected the front end .mdb correctly and it said that the link to the server database was working when I hit the test button, but it just didn’t do anything. I ended up creating a DSN, linking to the tables manually with Linked Table Manager, then writing some code to rename all the linked tables to remove the dbo_ prefix. My question is whether the tool should work to relink databases like this. And if so, if you have any idea what I did wrong. I’m heading in now to do it for real..... Regards, Phil
A. Hi Phil,
The answer is yes, you should be able to do this.
Proceed as follows using a NEW or RESET copy of MUST.
1. Enter server details and test server connection.
2. On the same server screen use the button at the bottom of the screen “Option to load information from an existing SQL Server….”. This will load the table list from the SQL Server with correct connection information.
3. Select the target access application. Do not analyse the application but move to step 4.
4. Go straight to the “Re-link Access Application Icon” and relink the access database.
Let me know how you get on with this.
The product that we are talking about here is called MUST, an Access tool developed by Andy Couch, a fellow Access MVP. Read more
To use the product you place the MUST MDE file in the same folder as your Access database(s), open it up, identify Access, nominate your SQL Server database and you are away.
Office Access MVP from Australia
To make this upsizing software work, you will need Access 2010 or 2007 and you will need SQL Server 2005 or 2008 and you will need Administrator rights on that server.
For MUST+Web you will need Visual Studio 2005 or 2008
The best way to find out about the software is to view our videos or download and try the trial version.