microsoft reporting services projects 2017 download

• Awards Season
• Big Stories
• Pop Culture
• Video Games
• Celebrities

Collaborative Editing Made Easy: Exploring Online Word Editors for Microsoft

In today’s digital age, collaboration is key to success in any project or task. Whether you’re working on a presentation, a report, or even a simple document, having the ability to collaborate seamlessly with others is crucial. Microsoft Word has long been the go-to word processing software for many professionals and students alike. However, with the rise of online tools and the need for remote collaboration, online word editors for Microsoft have gained popularity. In this article, we’ll explore some of the best online word editors available and how they can enhance your collaborative editing experience.

Google Docs: The Powerhouse of Collaboration

When it comes to online word editors, Google Docs stands out as a powerhouse of collaboration. With its intuitive interface and real-time editing capabilities, Google Docs allows multiple users to work on a document simultaneously. Users can see changes made by others in real-time and even leave comments and suggestions directly within the document. Additionally, Google Docs automatically saves changes as you type, ensuring that no work is lost even in case of unexpected disruptions.

One of the major advantages of using Google Docs as an online word editor for Microsoft is its compatibility with various file formats. You can easily import your existing Word documents into Google Docs without any formatting issues. Furthermore, you can export your finished work back to Word format if needed.

Office Online: The Familiarity of Microsoft

For those who prefer sticking to familiar interfaces and functionalities but still want the convenience of online collaboration, Office Online is an excellent choice. Developed by Microsoft itself, Office Online offers web-based versions of popular applications like Word, Excel, PowerPoint, and more.

With Office Online’s online word editor for Microsoft Word specifically, users can access their documents from anywhere with an internet connection. It provides many features similar to its desktop counterpart while also enabling real-time co-authoring and sharing options. Users can invite others to collaborate on a document and work together seamlessly, just like they would in the desktop version of Microsoft Word.

Zoho Writer: Feature-Rich and User-Friendly

Zoho Writer is another online word editor for Microsoft that deserves recognition for its feature-rich environment and user-friendly interface. Apart from the standard word processing features, Zoho Writer offers some unique functionalities that enhance collaboration.

One notable feature of Zoho Writer is the ability to integrate with cloud storage services like Google Drive and Dropbox. This means you can access your files directly from these storage platforms within Zoho Writer, without the hassle of downloading and uploading documents manually. Additionally, Zoho Writer offers robust sharing options, allowing you to control access permissions for collaborators.

OnlyOffice: All-in-One Collaboration Suite

Last but not least, OnlyOffice is an online word editor that goes beyond just document editing. It is a comprehensive collaboration suite that includes document editing, spreadsheets, presentations, project management tools, and more.

With OnlyOffice’s online word editor for Microsoft Word documents, users can collaborate in real-time while enjoying advanced formatting options and track changes functionalities. It also provides seamless integration with popular cloud storage services and allows users to co-edit documents using their preferred device – be it a computer or a mobile device.

In conclusion, collaborative editing has become easier than ever with the availability of online word editors for Microsoft Word documents. Whether you choose Google Docs for its real-time collaboration capabilities or prefer Office Online for its familiarity with Microsoft interfaces, these online tools offer convenience and efficiency in remote collaborations. Additionally, tools like Zoho Writer and OnlyOffice provide unique features that cater to specific needs while ensuring smooth collaboration among team members. So why limit yourself to traditional desktop-based editing when these online word editors can take your collaborative projects to new heights?

This text was generated using a large language model, and select text has been reviewed and moderated for purposes such as readability.

MORE FROM ASK.COM

Internet Explorer was retired on June 15, 2022

Microsoft SQL Server 2017 Reporting Services

SQL Server Reporting Services is a server-based reporting platform that provides comprehensive reporting functionality.

Important! Selecting a language below will dynamically change the complete page content to that language.

14.0.601.20

Date Published:

SQLServerReportingServices.exe

• Paginated reports optimized for document generation and printing.
• Mobile reports optimized for mobile devices, with responsive layout that adapts to different devices and the different ways you hold them.
• A modern web portal you can view in any modern web browser.

System Requirements

Supported Operating Systems

Windows Server 2016, Windows 10, Windows Server 2012 R2, Windows Server 2012, Windows 8, Windows 8.1, Windows Server 2019

• .NET Framework 4.5.2 or later
• SQL Server Database Engine (2012 SP4 or later), to store the report server database
• Download the Evaluation Edition of Microsoft SQL Server

Install Instructions

• Install SQL Server Reporting Services (SQLServerReportingServices.exe)
• Configure your report server using Report Server Configuration Manager

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Install SQL Server Reporting Services

• 13 contributors

SQL Server Reporting Services installation involves server components for storing report items, rendering reports, and processing of subscription and other report services.

Download SQL Server 2022 Reporting Services from the Microsoft Download Center.

Download SQL Server 2019 Reporting Services from the Microsoft Download Center.

Download SQL Server 2017 Reporting Services from the Microsoft Download Center.

Looking for Power BI Report Server? See Install Power BI Report Server .

Upgrading or migrating from a SQL Server 2016 or earlier version of Reporting Services? See Upgrade and Migrate Reporting Services .

Before you begin

Before you install Reporting Services, review the Hardware and software requirements for installing SQL Server .

Install your report server

Installing a report server is straightforward. There are only a few steps to install the files.

You don't need a SQL Server Database Engine server available at the time of install. You do need one to configure Reporting Services after install.

Find the location of SQLServerReportingServices.exe and launch the installer.

Select Install Reporting Services .

Choose an edition to install and then select Next .

For a free edition, choose either Evaluation or Developer from the drop-down.

Otherwise, enter a product key. Find the product key for SQL Server Reporting Services .

Read and agree to the license terms and conditions and then select Next .

You need to have a Database Engine available to store the report server database. Select Next to install the report server only.

Specify the install location for the report server. Select Install to continue.

The default path is C:\Program Files\Microsoft SQL Server Reporting Services.

After a successful setup, select Configure Report Server to launch the Report Server Configuration Manager.

Configure your report server

After you select Configure Report Server in the setup, you're' presented with Report Server Configuration Manager . For more information, see Report Server Configuration Manager .

You need to create a report server database to complete the initial configuration of Reporting Services. A SQL Server Database server is required to complete this step.

Creating a database on a different server

If you're creating the report server database on a database server on a different machine, you need to change the service account for the report server to a credential that is recognized on the database server.

By default, the report server uses the virtual service account. If you try to create a database on a different server, you may receive the following error on the Applying connection rights step.

System.Data.SqlClient.SqlException (0x80131904): Windows NT user or group '(null)' not found. Check the name again.

To work around the error, you can change the service account to either Network Service or a domain account. Changing the service account to Network Service applies rights in the context of the machine account for the report server.

For more information, see Configure the report server service account .

Windows Service

A Windows service is created as part of the installation. It's displayed as SQL Server Reporting Services . The service name is SQLServerReportingServices .

Default URL reservations

URL reservations are composed of a prefix, host name, port, and virtual directory:

An example of the complete URL string might be as follows:

https://+:80/reportserver , provides access to the report server.

https://+:80/reports , provides access to the web portal.

If you're accessing the report server from a remote machine, you want to make sure you've configured any firewall rules if there's a firewall present.

You need to open up the TCP port that you've configured for your Web Service URL and Web Portal URL. By default, these are configured on TCP port 80.

Additional configuration

To configure integration with the Power BI service so you can pin report items to a Power BI dashboard, see Integrate with the Power BI service .

To configure email for subscriptions processing, see E-Mail settings and E-Mail delivery in a report server .

To configure the web portal so you can access it on a remote computer to view and manage reports, see Configure a firewall for report server access and Configure a report server for remote administration .

Related information

For information on how to install SQL Server Reporting Services native mode, see Install Reporting Services native mode report server .

For information on how to install SQL Server 2016 Reporting Services (and earlier) in SharePoint integration mode, see Install the first Report Server in SharePoint mode .

With your report server installed, begin to create reports and deploy those to your report server. For information on how to start with Report Builder, see Install Report Builder .

To create reports using SQL Server Data Tools, download SQL Server Data Tools .

More questions? Try asking the Reporting Services forum

Was this page helpful?

Submit and view feedback for

Additional resources

SQL Server Reporting Services SSRS 2017 Installation and Configuration Setup

By: scott murray.

SQL Server Reporting Services has evolved into a full-fledged reporting solution which maintains a strong presence in the current reporting, business intelligence, and reporting analytics market space.

Explanation

SQL Server Reporting Services or SSRS has been the go to reporting solution for SQL Server for almost a decade now. When it was first introduced, folks were used to working with Microsoft Access, and Crystal Reports was just storming into the reporting world.  Business Intelligence and its related processes were also beginning to shape the way data was presented. In many organizations, the ease of development, the web front end, and the security integration with Active Directory allowed SSRS to reign in as the reporting tool of choice. Still today it is a highly competent and able tool which has grown in feature availability and overall usage. For this tutorial we will focus on SQL Server 2017, but many of the features to be highlighted in this tutorial series apply to SQL Server 2016 and prior versions.

Installation and Configuration

Of course, the first steps that needs to be completed is installing SSRS. In the past SSRS was an integral part of the SQL Server installation process. For 2017, Report Services is now a separate, stand-alone install process. You first must download the SQL Server Reporting Services install file from https://www.microsoft.com/en-us/download/details.aspx?id=55252 . The install process is like just about any other install process you complete; however, at the end of the install, either SSRS can be configured now or at a later time. We will not cover the individual installation screens as the they are covered in the installation instructions on the download site; we will however jump right into the configuration.

The configuration process requires that you already have a SQL Server in order to house the Reporting Services databases. The location of the reporting Services database is completely up to your organization’s requirements and needs; it can be on the same server as reporting-services although there will be contention issues. As an alternative you can place Reporting Services on one machine and then connect to another server to hold the databases.

To run the SSRS Configuration Manager, you will go to the Programs menu and select SQL Server Reporting Services Configuration Manager.  Initially, a connection to the SSRS service must be made.

After connecting to the SSRS service, step 1 is instructing SSRS configuration manager which account to use for the SSRS service. This service account is actually set during the install, but can be changed to any local or Windows account (AD account).

The report manager and the reports web portal URL’s are assigned subsequently. In the below example, the virtual directory is set to ReportServer_SSRS and the default port for the website is set to port 80.

Our next step is to actually set up connection to the SSRS databases. This link can be to existing databases or you can create two new databases. SSRS requires that you have both a regular SSRS database and a SSRS Temp database as shown below. These databases can be located on any server.

Completing the SMTP email settings would be the ensuing process to complete. For this item, the sender address, the SMTP server, and the Authentication must be completed.

Optionally, an Execution Account can be specified which allows for connectively to images on remote servers and connections to credential-less data sources.

After configuring the execution account (for our killer app!), the next step is to backup (and when needed restore) the SSRS encryption keys. It is important that the key be backed up for both backup purposes and for the instance when SSRS is moved to a new server. This key preserves the security elements for the folders and reports on the SSRS website. We will discuss security in more detail later in this tutorial series.

In a way similar to the Execution Account, a subscription account can also be defined to allow subscriptions to use a common account to access file shares. This account will be used by the subscription jobs to write files to the share specified in the subscription.

If this server is included in an entire SSRS scale-out farm setup, then this instance can be added as part of a larger deployment process.

The final and likely one of the newest steps in the configuration manager is to integrate SSRS with Power BI. Linking to Power BI allows users to publish (or Pin) reports to Power BI.

This screen establishes the connection to your organization’s Power BI site and allows for the pinning of report to the Power BI site.

Once SSRS is configured for use, the SSRS site is up and read to go!

Development Tools

Now that the site is up and running, we need to explore the tools that are available to develop reports for the report server. You actually have two main choices when deciding which tools to develop reports. For light weight developers, the Report Builder tool can be used to develop reports whereas more cutting-edge developers generally use SQL Server Data Tools for Business Intelligence or SSDT-BI for short.

Both tools can be directly downloaded from Microsoft at:

• SSDT-BI - https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt
• Report Builder - https://www.microsoft.com/en-us/download/details.aspx?id=53613

Please note that these links change often as Microsoft releases updated editions of each of the tools.

As of this writing, the Report Builder is noted for SQL 2016, but in a testing environment, I have been able to connect to SQL 2017. It should also be noted that Report builder can also be downloaded directly from your SSRS web portal as shown below.

For SSDT-BI, it is generally recommended that you implement SSDT-BI as part of your Visual Studio installation. The Community Edition of Visual Studio 2017 can easily be used to house the SSDT-BI add-in. If you have a higher (i.e. paid) edition of Visual Studio, the add-in can certainly be supplemented as part of that edition. Once installed, several BI projects will be available in Visual Studio, as illustrated below.

Both of these tools are capable of developing reports for SSRS; most advanced developers will prefer to use SSDT-BI in Visual Studio. As such, in this series of tutorials we will use SSDT-BI. However, Report Builder is widely used by many data analysts to produce a quick report. Furthermore, a Report Builder developed report can be easily imported into a Visual Studio project for more advanced development, if necessary.

Installing Reporting Services and then subsequently the development tool, SSDT-BI are the first steps to working with SSRS. In the next phase in our tutorial series, we will use SSDT-BI to work through creating a new report and then move directly into reviewing the various options surrounding available data sources and their utilization in SSRS.

Additional Information

• In our next tutorial we will cover data sources.
• SSRS Stand Alone Installation: https://www.mssqltips.com/sqlservertip/4852/sql-server-reporting-services-standalone-installation/
• https://www.mssqltips.com/sqlservertutorial/227/install-reporting-services/
• https://www.mssqltips.com/sqlservertip/3469/install-and-configure-sql-server-reporting-services-2012-sp1-and-2014-in-sharepoint-integrated-mode-part-1/

Next >>

Comments for this article.

The Maximum Impact Solutions Blog

Training dept, mizokunimto.

Search code, repositories, users, issues, pull requests...

Provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications

Git repo for SQL Server Reporting Services and Power BI paginated report samples, and community projects

microsoft/Reporting-Services

Name already in use.

Use Git or checkout with SVN using the web URL.

Work fast with our official CLI. Learn more about the CLI .

• Open with GitHub Desktop
• Download ZIP

Sign In Required

Please sign in to use Codespaces.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

• 154 commits

Reporting Services

Git repo for SQL Server Reporting Services samples and community projects

Reporting Services PowerShell Tools

In order to provide a better install experience the PowerShell scripts have been moved to https://github.com/Microsoft/ReportingServicesTools

Reporting Services Custom Security Sample

This project will help you to get started with how to deploy a custom security extension to SQL Reporting Services. For more details please check out the read me document in this folder CustomSecuritySample .

Reporting Load Test

Contains a Visual Studio Load Test 2015 solution to execute synthetic load for SQL Server Reporting Services 2016 https://github.com/Microsoft/Reporting-Services-loadtest

Paginated Report Samples

Contains several sample Power BI paginated reports to download and explore. They demonstrate typical ways you can use paginated reports. For more details please check out this article Paginated Report Samples . This folder contains the following paginated report samples :

• CountrySalesPerformance
• OrganizationExpenditures
• RegionalSales

Code Of Conduct

This project has adopted the Microsoft Open Source Code of Conduct . For more information see the Code of Conduct FAQ or contact o[email protected] with any additional questions or comments.

Code of conduct

Security policy, contributors 15.

• TypeScript 0.4%
• PowerShell 0.3%

Software + Imagination

How to Open an SSRS RDL Report in Visual Studio 2017 and 2019

Let’s look at how to open an SSRS RDL Report in Visual Studio 2017 and Visual Studio 2019.

First, download the Microsoft Reporting Services Project extension at:

https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftReportProjectsforVisualStudio

We see this applies to Visual Studio 2017 and 2019:

You will see the file downloaded. Open it:

You will see:

Be sure to close any Visual Studio instances running. Click Install:

We can now create Report Server Projects in Visual Studio.

In Visual Studio 2017:

In Visual Studio 2019:

Once created, we see:

From here, we can add or create RDL reports:

I AM SPENDING MORE TIME THESE DAYS CREATING YOUTUBE VIDEOS TO HELP PEOPLE LEARN THE MICROSOFT POWER PLATFORM.

IF YOU WOULD LIKE TO SEE HOW I BUILD APPS, OR FIND SOMETHING USEFUL READING MY BLOG, I WOULD REALLY APPRECIATE YOU SUBSCRIBING TO MY YOUTUBE CHANNEL .

THANK YOU, AND LET'S KEEP LEARNING TOGETHER.

https://www.youtube.com/carldesouza

Carl de Souza is a developer and architect focusing on Microsoft Dynamics 365, Power BI, Azure, and AI.

Related Posts:

• Using the Power Platform CLI with Power Pages
• Configuring ESLint Semi-Colons Rule
• Embedding Power Automate Flows Inside Power BI

One Response to How to Open an SSRS RDL Report in Visual Studio 2017 and 2019

Hi, I am using VS community 2019 and followed your steps by installing Microsoft Reporting Services Project. I am able to create a new Report, but I am struggling with the Data Connection which I can’t find Embedded Connection Type = Microsoft Dynamics 365 Fetch as I can find it in VS community 2015. Are there any changes or how do I need to set the connection so that I can create a report with FetchXML ?

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Visual Studio 2017 - SSDT

SSCrazy Eights

Points: 9090

More actions

May 2, 2017 at 4:01 am

Hi, I'm hoping someone can tell me that I'm mistaken and have missed something but I've installed Visual Studio Professional 2017 (15.1 - 26403.7) Release.

The project template for SSIS packages is missing so I installed SSDT,taking the installer from here https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt This installed successfully, however there is still no template for SSIS projects and attempting to open an existing VS2012/2015 SSIS projects results in an error.

So I started to look around and from what I can see VS 2017 does not yet support SSIS projects, is that right? or am I missing something? I came across this https://developercommunity.visualstudio.com/content/problem/25001/cannot-open-integration-services-ssis-projects.html

Which to me indicates SSAS and SSRS are supported via extensions but not SSIS. Please say I'm missing something. 

Check out my blog http://www.sqlservercentral.com/articles/Best+Practices/61537/

Points: 99116

May 2, 2017 at 4:09 am

SSIS has not been released yet for VS 2017. Probably because the latest SQL 2017 CTP version doesn't support SSIS yet either (due in the next month or 2 I think?).

It'll come; my personal guess is when SSIS is available for SQL 2017.

EDIT/P.S. ARGH!!! What made you choose to use the abomination of a font! Mine EYES!!! 😉

Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does. Larnu.uk

Phil Parkin

Points: 246405

May 2, 2017 at 5:42 am

NicHopper - Tuesday, May 2, 2017 4:01 AM Hi, I'm hoping someone can tell me that I'm mistaken and have missed something but I've installed Visual Studio Professional 2017 (15.1 - 26403.7) Release. The project template for SSIS packages is missing so I installed SSDT,taking the installer from here https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt This installed successfully, however there is still no template for SSIS projects and attempting to open an existing VS2012/2015 SSIS projects results in an error. So I started to look around and from what I can see VS 2017 does not yet support SSIS projects, is that right? or am I missing something? I came across this https://developercommunity.visualstudio.com/content/problem/25001/cannot-open-integration-services-ssis-projects.html Which to me indicates SSAS and SSRS are supported via extensions but not SSIS. Please say I'm missing something.  Thanks, Nic

Your suspicions are confirmed on the SSDT 2017 page here .

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

May 2, 2017 at 6:27 am

Thanks for the replies.

As for the font - I thought I'd Jazz it up a bit. 🙂

pat.lendrum

SSC Enthusiast

Points: 194

May 29, 2018 at 6:19 pm

​I have found a SOLUTION!!!  This is for 2012 solution/project but should work for all...

1) Install SSDT for VS 2017; I ONLY installed Integration services (NOT Analysis or Reporting Services)

2) Restart Computer after install

3) Open Visual Studio-->Tools-->Extensions and Updates-->ENABLE Integration services extension (NEVER knew this was an extension/option)

4) Restart Visual Studio

5) Open solution.  The Project may still error; if it does, right click on the project and rebuild project.  It should now open and have the version in parenthesis

May 30, 2018 at 1:47 am

pat.lendrum - Tuesday, May 29, 2018 6:19 PM ​I have found a SOLUTION!!!  This is for 2012 solution/project but should work for all... 1) Install SSDT for VS 2017; I ONLY installed Integration services (NOT Analysis or Reporting Services) 2) Restart Computer after install 3) Open Visual Studio-->Tools-->Extensions and Updates-->ENABLE Integration services extension (NEVER knew this was an extension/option) 4) Restart Visual Studio 5) Open solution.  The Project may still error; if it does, right click on the project and rebuild project.  It should now open and have the version in parenthesis

The solution was to wait for the RTM release? Now that it's out, yes SSIS is part of the suite. The OP was using a CTP version of SSDT; which didn't support SSIS at the time.

May 30, 2018 at 12:04 pm

Thom A - Wednesday, May 30, 2018 1:47 AM pat.lendrum - Tuesday, May 29, 2018 6:19 PM ​I have found a SOLUTION!!!  This is for 2012 solution/project but should work for all... 1) Install SSDT for VS 2017; I ONLY installed Integration services (NOT Analysis or Reporting Services) 2) Restart Computer after install 3) Open Visual Studio-->Tools-->Extensions and Updates-->ENABLE Integration services extension (NEVER knew this was an extension/option) 4) Restart Visual Studio 5) Open solution.  The Project may still error; if it does, right click on the project and rebuild project.  It should now open and have the version in parenthesis

Yes, however, when you install SSDT for Integration services this is DISABLED by default which throws the SAME error.  You need to manually go to tools, enable and then you can do it.  WHY the f*** does MSFT disable a component that I am specifically installing?!?!  That is where this thread came from and NO answers as to why it still did not open older package version inherently.  i should NOT have to enable that SSDT extension after installing (enabled should be the default).

May 30, 2018 at 1:00 pm

pat.lendrum - Wednesday, May 30, 2018 12:04 PM Thom A - Wednesday, May 30, 2018 1:47 AM pat.lendrum - Tuesday, May 29, 2018 6:19 PM ​I have found a SOLUTION!!!  This is for 2012 solution/project but should work for all... 1) Install SSDT for VS 2017; I ONLY installed Integration services (NOT Analysis or Reporting Services) 2) Restart Computer after install 3) Open Visual Studio-->Tools-->Extensions and Updates-->ENABLE Integration services extension (NEVER knew this was an extension/option) 4) Restart Visual Studio 5) Open solution.  The Project may still error; if it does, right click on the project and rebuild project.  It should now open and have the version in parenthesis

SSIS isn't disabled by default... I installed it on 3, machines last month, SSDT comes with all 3 BI tools out the box. Sounds like you didn't tick the right box I'm afraid.

pat.lendrum - Wednesday, May 30, 2018 12:04 PM Yes, however, when you install SSDT for Integration services this is DISABLED by default which throws the SAME error.  You need to manually go to tools, enable and then you can do it.  WHY the f*** does MSFT disable a component that I am specifically installing?!?!  That is where this thread came from and NO answers as to why it still did not open older package version inherently.  i should NOT have to enable that SSDT extension after installing (enabled should be the default).

I did not have to do this when I installed SSDT 2017.

May 30, 2018 at 1:23 pm

Phil Parkin - Wednesday, May 30, 2018 1:00 PM pat.lendrum - Wednesday, May 30, 2018 12:04 PM Yes, however, when you install SSDT for Integration services this is DISABLED by default which throws the SAME error.  You need to manually go to tools, enable and then you can do it.  WHY the f*** does MSFT disable a component that I am specifically installing?!?!  That is where this thread came from and NO answers as to why it still did not open older package version inherently.  i should NOT have to enable that SSDT extension after installing (enabled should be the default).

I definitely ticked the 1st box for integration services and left RS and AS unticked...

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply