Changes in f078ff8: Updated ConnectionStringRW (markdown)

				FAQ/Questions/ConnectionStringRW.md
			
          @@ -46,24 +46,11 @@ End Class

           ```

          +##How ConnectionStringRW works

          -##Question

          +1) If ConnectionStringRW is not assigned, Izenda uses Driver.ConnectionString for all operations against DB

          -How do I add Read-Write user permission to DB?

          -

          -##Answer

          -

          -Using 'ConnectionStringRW' property, user permissions to DB can be specified. This property should be assigned similarly to normal connection string as below - in the initialization of reporting.

          -

          -

          -

          -

          -

          -

          -If it's not assigned, Izenda as before uses Driver.ConnectionString for all operations against DB

          -

          -

          -4) If ConnectionStringRW is also assigned, then Izenda will

          +2) If ConnectionStringRW is also assigned, then Izenda will

             a) Use Driver.ConnectionString for Read-Only operations against DB, thus Driver.ConnectionString can have ReadOnly access to the DB

          @@ -78,9 +65,9 @@ If it's not assigned, Izenda as before uses Driver.ConnectionString for all oper

               - Create/Save/Delete ReportSets in Reports table in Database mode

          -Here is the video explaining how to create ReadOnly connection string in MSSQL: http://www.screencast.com/users/IzendaReports/folders/Temporary/media/9a2e633c-bbc7-4c47-9425-8df36d36e368

          -

          -6) Here is video demonstrating how installation works when Driver.ConnectionStringRW is assigned for read-write operations, and Driver.ConnectionString has ReadOnly access: http://www.screencast.com/users/IzendaReports/folders/Temporary/media/a04a117c-89d1-40f3-8053-55d0d7586d1a

          +[Here](http://www.screencast.com/users/IzendaReports/folders/Temporary/media/9a2e633c-bbc7-4c47-9425-8df36d36e368) is the video explaining how to create ReadOnly connection string in MSSQL 

          +[Here](http://www.screencast.com/users/IzendaReports/folders/Temporary/media/a04a117c-89d1-40f3-8053-55d0d7586d1a) is video demonstrating how installation works when Driver.ConnectionStringRW is assigned for read-write operations, and Driver.ConnectionString has ReadOnly access: 

          -Really it can be used always. General case is just safety improvement - if user specifies ConnectionStringRW, and uses read-only DB account for usual Driver.ConnectionString - he can be 100% sure that users will not be able to modify anything in DB by any means - like using SQL injections. Just because everything which user can input - goes to DB via read-only connection string.

          +##Usage

          +ConnectionStringRW can be used always. General case is just safety improvement - if user specifies ConnectionStringRW, and uses read-only DB account for usual Driver.ConnectionString - he can be 100% sure that users will not be able to modify anything in DB by any means - like using SQL injections. Just because everything which user can input - goes to DB via read-only connection string.

...	...	@@ -46,24 +46,11 @@ End Class
46	46	```
47	47
48	48
	49	+##How ConnectionStringRW works
49	50
50		-##Question
	51	+1) If ConnectionStringRW is not assigned, Izenda uses Driver.ConnectionString for all operations against DB
51	52
52		-How do I add Read-Write user permission to DB?
53		-
54		-##Answer
55		-
56		-Using 'ConnectionStringRW' property, user permissions to DB can be specified. This property should be assigned similarly to normal connection string as below - in the initialization of reporting.
57		-
58		-
59		-
60		-
61		-
62		-
63		-If it's not assigned, Izenda as before uses Driver.ConnectionString for all operations against DB
64		-
65		-
66		-4) If ConnectionStringRW is also assigned, then Izenda will
	53	+2) If ConnectionStringRW is also assigned, then Izenda will
67	54
68	55	a) Use Driver.ConnectionString for Read-Only operations against DB, thus Driver.ConnectionString can have ReadOnly access to the DB
69	56
...	...	@@ -78,9 +65,9 @@ If it's not assigned, Izenda as before uses Driver.ConnectionString for all oper
78	65	- Create/Save/Delete ReportSets in Reports table in Database mode
79	66
80	67
81		-Here is the video explaining how to create ReadOnly connection string in MSSQL: http://www.screencast.com/users/IzendaReports/folders/Temporary/media/9a2e633c-bbc7-4c47-9425-8df36d36e368
82		-
83		-6) Here is video demonstrating how installation works when Driver.ConnectionStringRW is assigned for read-write operations, and Driver.ConnectionString has ReadOnly access: http://www.screencast.com/users/IzendaReports/folders/Temporary/media/a04a117c-89d1-40f3-8053-55d0d7586d1a
	68	+[Here](http://www.screencast.com/users/IzendaReports/folders/Temporary/media/9a2e633c-bbc7-4c47-9425-8df36d36e368) is the video explaining how to create ReadOnly connection string in MSSQL
84	69
	70	+[Here](http://www.screencast.com/users/IzendaReports/folders/Temporary/media/a04a117c-89d1-40f3-8053-55d0d7586d1a) is video demonstrating how installation works when Driver.ConnectionStringRW is assigned for read-write operations, and Driver.ConnectionString has ReadOnly access:
85	71
86		-Really it can be used always. General case is just safety improvement - if user specifies ConnectionStringRW, and uses read-only DB account for usual Driver.ConnectionString - he can be 100% sure that users will not be able to modify anything in DB by any means - like using SQL injections. Just because everything which user can input - goes to DB via read-only connection string.
	72	+##Usage
	73	+ConnectionStringRW can be used always. General case is just safety improvement - if user specifies ConnectionStringRW, and uses read-only DB account for usual Driver.ConnectionString - he can be 100% sure that users will not be able to modify anything in DB by any means - like using SQL injections. Just because everything which user can input - goes to DB via read-only connection string.