I'm .net developer and have no experience with Visual Foxpro. I have to migrate old system use Visual Fox upto Asp.Net. The old system already use SQL Server to store data, but there are many reports must be migrated, if i can connect to the processed report data. It's seem to be save lot of my effort.
Pls, give me a suggest for this situation.
http://www.vfpconversion.com/Vfp2NetReports.aspx#4
they have a tool that converts foxpro reports to ssrs or crystal reports
There's no magic bullet I'm afraid. You will have to re-do them using, for example, SQL Server Reporting Services.
Related
I'm trying to get data from api and insert them into a SQL Server .sdf database file, but I'm not sure how to do it especially that I'm using Windows forms on Visual Studio 2010
Can someone help me ?
This is a very broad question, however, at a very high level, you will need to open up a connection to the SQL Server Database and use a data access technology such as ADO.NET or EntityFramework to work with the objects in the database.
See the answer in this thread for an example of working with ADO.NET.
I am currently creating a database for my project and was wondering where I should save the table. Should I just save it in documents (D:\Documents) or should I save it in the same folder where my project is saved (D:\Documents\Visual Studio 2015\Projects\ALevelCompUnit3)? I was hoping to develop it at school.
Also, the school only provides Visual Basic 2008; would I have to change the framework to do it at school?
SQL Server Express in fact is a light weight version of the SQL server engine that is stored locally on your file system under the extension .mdf. Within this file you will be saving things like tables, views and stored procedures. You can move this file around similar to other traditional file types and where you store it while your developing your application is up to you. If, and when you application grows you may consider moving it over to a full version of SQL Server and there are tools to quickly migrate over. In regards to your Visual Studio versions - Using 2015 at home and switch over to 2008 at school will be a little painful. There are many features of 2015 that are not available in 2008. You should be able to access the .mdf file but your experience will not be as powerful in terms of capabilities.
Ive installed SSRS on my local machine, we want to test it before we deploy it for the whole system. It is running off SQL 2012 Express edition (this maybe why- however if it is then ssrs is virtually unusable on express?).
I keep getting error messages saying: This feature is not available in this edition of SSRS.
-Its when I do things like:
save a dataset?
Try to access the report builder?
try to update security settings?
Any Idea's guys?
Thank you in Advance!
Take a look at the SSRS Edition comparison chart here: http://msdn.microsoft.com/en-us/library/cc645993.aspx#Reporting
Express lacks a lot of features, and is not going to suitably reflect what you'll be seeing with Standard or Enterprise edition. If your Production plans involve a higher tier sku, I'd suggest skipping this Express test, and just grab a 180 day trial of SQL Server and try out the same version you'll be using in Production.
I'm fairly newb when it comes to programming and even newer when it comes to database management and integration.
So I have a VB.NET Windows Application that uses a SQL Database. I use LINQ to SQL to fill datagridviews in windows that show table data and also use LINQ to SQL to save data to the database.
All works wonderfully however...
When I publish the application, the database isn't external as far as I can tell. It seems to build itself into the application so once the application is installed, the database is there, it views and saves data, but if the computer crashes or the application is uninstalled, all that data is going to be lost without a way to back it up.
I'm using Visual Studio 2010 Express. I created the SQL Database in VS2010-Exp as well. I feel like there's something simple I'm missing here. When the application gets published and then installed, where is the physical database going?
Thanks!
It is running as part of the application. If you wanted a separate, central database, you would need to have an instance of SQL server running in some accessible location.
I recently got a new primary computer. On my old one, I was working with MS Visual Studio 2008 (or maybe an older version - I can't remember now). I had managed to get SQLite working with it and was in the start/middle of building an application.
On the new computer, I now have MS Visual Studio 2010. I have had problems getting SQLite to work with it. Honestly, I haven't tried super hard yet, because I realized I pretty much want to completely redesign this application anyway and it got me thinking... do I really want to use SQLite or some other SQL? MS SQL (or is it called SQL Server)? MySQL?
My end goal is to have an application that can be installed by the user with one .msi file and the user should not have direct access to the database (although at this stage, that is a secondary concern).
It seems like MS SQL / SQL Server is the easiest since it's also an MS product.... Would love some opinions!
(along with the opinions, I'd also love to be pointed to current instructions... I'm a programmer, I'm not a "coding environment setup" person and have always struggled with this. All I want is to get in there and write my application!)
Thanks in advance!
-Adeena
PS... I'm currently working with C# and would prefer to stick with it, but could easily do this in C++ (I'm fluent in all the flavors of C) if that makes a difference with the database.
SQL Server would be a good choice by the sounds of what you're after. Try the express version - it's free, good for development and prototyping and integrates really well with Visual Studio.
The SQL Server Management Studio tool is excellent. I use this to create the databases I need and then use Visual Studio to manage them (saves switching windows and running both applications when you're working in VS all day anyway). I used to have my issues with the old Enterprise manager software but things really seems to have stepped up for SQL Server 2008 and the new management studio.
Like the title of your question suggests, you're wanting to use this with Visual Studio. If you decide to do use SQL Server then you should:
Download the express edition
Download SQL Server management studio
Create a database
In Visual Studio - click View -> Server explorer -> right click Data connections and add connection. Select MS SQL Express and choose localhost as your server. You can then select the database you created using the management studio.
There you have it - integration with VS.
You say you're using C#.Net - well SQL server and .Net go hand-in-hand. Obviously you can hook up to other third party databases but SQL was really made to work with this stuff. It's a powerful database engine and will do everything you'll ever need as well as being well supported by Microsoft and the wider community.
If your final goal is to have hands-off single-click installation then I don't think SQL Server Express is your best bet because it's not a file-based embedded database. It's a great db and very easy to work with, but when it comes to deployment still takes some installation effort. You could try one of: SQL Server Compact Edition, SQLite or Firebird Embedded.
SQLExpress is free and for development purposes is pretty much interchangeable with the full SQLServer
http://www.microsoft.com/express/Database/
SQL SERVER seems to be the logical one.