Transitioning from MS Access to MS SQL Server

[Lou_Reed]

Okay, here is my situation. I got an assignment to create a new database. That is I will do. However, it must be in Microsoft SQL Server. In the end


that is the database that it will be in.

I can start out now in MS Access and then port it over to MS SQL server as soon as the equipment where I work is available. It seems the equipment
is not available now and since I work for the government it is unlikely to be available soon; it will be available eventually.

So is it good idea to start out working on this in MS Access and wait for SQL Server to come on line or should it wait and do the whole thing in SQL server.

Any help appreciated.

Thanks in advance.

Respectfully,

Lou Reed

[ItsMe]

Use SQL Server Express on your development machine. SQL Server Management Studio is the application you will want to use as an RDBMS. This post might offer some insight ...
https://www.accessforums.net/access/...tml#post279655

You will need tables and stuff in your Microsoft SQL database. If you create tables in Access, you can convert them to schema using various tools. Any serious schemas will need to be created using more robust tools like Visual Studio or SSMS, itself. However, the following tool might get you started. Beware, I would not use it for complex constraints and I would not use it for exporting data from Access (more than a handful of rows). I would use it only for simple table structure. Also, understand that you will need to run (not install, both versions are part of the install) the 32 bit version in order to communicate with 32 bit Access.
https://msdn.microsoft.com/en-us/lib...=sql.110).aspx

[CJ_London]

also if developing initially in access read up on what won't port to sql server - lookups and multivalue fields come to mind. and there is no easy equivalent to the crosstab query.

You haven't said whether you will be using access as a front end or something else since sql server only provides a back end

[ssanfu]

also if developing initially in access read up on what won't port to sql server - lookups and multivalue fields come to mind.

Add to that, No spaces in names and no reserved words.