Interface for SQL Server database

Comments and ideas for software tools (ActiveX components)
to make a user interface for database.Do a google search

Madhivanan

Petteri wrote:
> Comments and ideas for software tools (ActiveX components)
> to make a user interface for database.|||Like this ;-)

http://www.google.fi/search?hl=fi&q...ogle-haku&meta=

Thank You, it helps

"Madhivanan" <madhivanan2001@.gmail.com> kirjoitti
viestiss:1149240372.946923.100540@.i39g2000cwa.goo glegroups.com...
> Do a google search
> Madhivanan
> Petteri wrote:
>> Comments and ideas for software tools (ActiveX components)
>> to make a user interface for database.|||Petteri (peter.rinne@.elperi.fi) writes:
> Comments and ideas for software tools (ActiveX components)
> to make a user interface for database.

Not really sure what the question is about, but if you work with ActiveX,
the obvious choice of client API is ADO.

But why ActiveX in this day and age? Why not .Net? Then you can use
ADO .Net, which despite the name is radically different from ADO -
and a whole lot better.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspxsql

Interactive Reporting

Software packages like Microsoft Small Business Accounting and Quickbooks offer a very powerful reporting module that lets end users change grouping, filtering, sorting, etc at run time (having it change the report dynamically infront of them). More importantly, their reporting tools let users click on details on the reports which opens the data in the form based portion of their software.

For example: If the end user pulls up a financial report, lets say "All Bills for February 07", the user get a report of all the bills that have gone out in that time frame. The end user can then click on the actual details in the report, and the Bill will come up in the Windows Forms portion of their software so they edit the bill, or create a new bill.

I have done a very limited amount of reporting in SQL Server, so I am not sure of how they were able to achieve this. If someone could give me some key words or ideas that I can bring up more information from in google, or even on here, I'd appreciate it.

Thanks in advance!

Have you taken a look at Report Builder yet?

Jarret

|||

Possibly... I will have to look that term up shortly to see what it actually is. So far I have just gone through visual studio biz intelligence projects and created new reporting projects. Ive done the wizards, created them manually, but I havent seen any kind of options to set that would actually let an end user interact with the report directly.

Interaction with VB/VBA

Hi there,

I've just started learning SQL - I already know a bit of VB/VBA and my aim is to become a software developer using both SQL and VB.

One question I have is how would the average programmer go about managing the database? Are SQL commands (queries/add record/make table etc) normally programmed and controlled in VB itself via the docommand.runSQL on the event triggers or are they managed from the SQL Server application themselves? Also, if there are any other comments on how VB works with SQL I'd be very interested to hear them.

My assumption is that the database commands are managed from VB and any automated download/import or export of data into or from the SQL database is scheduled from SQL server itself.

Many thanks for your time in reading.If you use MS SQL Server 7 or 2000 you can use Enterprise Manager to manage your databases. If you use SQL Server 2005 then you can use SQL Server Management Studio to do the same.

You can connect to your SQL Server db from VB6 with ADO and with ADO.NET from VB.NET.|||Many thanks for your reply - how about if you're using MS Access for the front end?|||ADO works fine when using Access as a front end. Even better if you use an adp. You can use the majority of your VBA functions from access if you like. However, a wise developer ports the lionshare of their data-centric business logic to the database itself.|||Many thanks for your reply - how about if you're using MS Access for the front end?

If you use MS Access the only difference will be that you'll manage your data from the MS Access environment, but you will still use ADO and ADO.NET from your VB applications.|||If you are using SQL 2K and you are wise you will avoid Enterprise Manager and use Query Analyser. EM is a GUI, QA allows programmatic access to the database - much more powerful and much more flexible.

DBAs don't typically use Access or EM to manage a SQL Server db but YMMV depending on how much control you are looking for.

HTH|||If you are using SQL 2K and you are wise you will avoid Enterprise Manager and use Query Analyser. EM is a GUI, QA allows programmatic access to the database - much more powerful and much more flexible.

DBAs don't typically use Access or EM to manage a SQL Server db but YMMV depending on how much control you are looking for.

HTH

I use EM daily to run hand-built queries and I do have programmatic access to my databases. I use QA too, but for the most things EM is just fine.|||yeah but if you script everything, you are more efficient because all you have to do is it hit f5 and you have less hassles when sql goes to a new version and your ui changes.

Integrating SQL RS 2005 into our apps

Microsoft Support

here is our scenario

We are an ISV that develops software products for our customers. We have two different flavors of Customers (Enterprise and Standard..) Ya, just like Microsoft

We would like to take SQL RS 2005 and integrate it within our apps

For our standard customers, we were thinking of packaging our canned reports into SQL 2005 Express Advanced versions

For our Enterprise customers, we were thinking of using the SQl 2005 Standard or Enterprise Reporting services.

As I was going down this path and making recommendations, I got an error trying to make this architecture work for us

Have SQL 2005 Report Server running on (Express- Advanced) talk to a SQL Express Catalog database on another box.

It appears that SQL 2005 Express can only work with local catalog database and local data sources. This is turning out to be a dampener to our migration to this server based reporting product for our low end customers.

Can you guys think of a workaround ? Our customer databases are going to be in SQL 2000 and it is going to be that way for a long time to come.. Meanwhile, we also want to adopt SQL2005 Reporting Services and move from Local reporting to Server based reporting.

Thoughts or ideas on helping me sell SQL 2005 Rs to folks here ?

Hi,

I am not from MS Support, but I think, that I am also allowed to answer? :-)

SQL Express wAF will only be allowed to access the local data storage - that is correct. You will be able to evaluate this in the feature comparison at www.microsoft.com/sql.

Why do you want a SQL Express for your Standard Users while connecting to another box?

Will this be the central data storage for your application? While couldn′t this be the Reporting Server also?

As another alternative you could use the reportviewer-control in your application.

Cheers,
Markus