Problems integrating reporting services into a web app

Hello

I have an existing web app on my web server, and reporting services on my app server. I'm trying to integrate the reports into the web app.

The problem is, when the user clicks 'execute report', the app, predictably, falls over, because the aspx page thinks it's on the same server as reporting services, whereas it's not.

Does anybody know how these requests from the aspx page can be redirected to a different server? The way I see it, if I can't get the integration working through url access, I'll have to use the soap api, which will involve dynamically creating drop downs for the report parameters, etc, which is moving away from utilising the advantages that reporting services brings!

Any thoughts would be greatly appreciated.

Thanks in advance
Dominic

Hi Dominic,

this article will help you embed the report in your web application:
http://msdn2.microsoft.com/en-us/library/ms153563.aspx

regards
Helen|||

Thanks for the reply helen. My problem is that in our architecture the client can't access the report server directly. I've decided to go with the reportviewer control instead.

Cheers

Dominic

Problems inserting decimal numbers

Hi,
I'm having trouble inserting a decimal numbre in SQL
Server. I have an app built on .Net.
I'm passsing the number "98.5" to a store procedure and
SQL Server is saving the number but like this 985.00.
What seems to be the problem?
The regional settings of the computer at first where:
decimal separator ","
List separator "."
group separator "."
I have changed them to
decimal separator "."
List separator ","
group separator ","
But is looks like its not working....
Please help....Manrique,
we know that SQL Server does not do that, so the answer is to find where the
values gets changed: is it changed by the application? Is it changed within
the stored procedure? I think that's what you need look at. Have the
stored proc return the value of the variable at various stages of the stored
proc, I believe you would see a "whoops" somewhere.
Quentin
"Manrique" <mulloa@.grupo-polymer.com> wrote in message
news:02ee01c38c31$d5624820$a301280a@.phx.gbl...
> Hi,
> I'm having trouble inserting a decimal numbre in SQL
> Server. I have an app built on .Net.
> I'm passsing the number "98.5" to a store procedure and
> SQL Server is saving the number but like this 985.00.
> What seems to be the problem?
> The regional settings of the computer at first where:
> decimal separator ","
> List separator "."
> group separator "."
> I have changed them to
> decimal separator "."
> List separator ","
> group separator ","
> But is looks like its not working....
> Please help....

Problems connectiong to a remote DB

Hello

I developed a vb.net win app which interacts with a sqlserver 2005 express DB.

When the DB is located in my local computer everything works just fine.

I'm trying to connect to a remote DB (mdf file that located on a remote server) but without any success.

I assume that a connectionstring change is needed, however I can't find what change to perform (I tried to insert the server IP address to the connectionstring but it didn't work either).

the app connectionstring looks like that:

connectionString

="Data Source=.\SQLExpress;AttachDbFilename=C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\DBName.mdf;Integrated Security=True;User Instance=False" providerName="System.Data.SqlClient" />

Hope someone can help me find the solution.

Since your question concerns a Windows Forms application, and not ASP.NET, you should ask it on theMSDN Forums.|||Try looking atwww.connectionstrings.com...|||Hi yarit, post the connection failure error message would help to solve the issue. You can also take a look at this post:
http://forums.asp.net/thread/1289341.aspx|||

Hello

Firstly thanks for all of your replies.

Now, I've succeeded to connect my app to a remote DBbut only in my company's network, the DB is located on a different machine in the company's network and I can connect to it using this connection string:

connectionString

="Data Source=Inner network IP address \ SQLEXPRESS;Database=DBName;Uid=xxx;Pwd=yyy;"providerName="System.Data.SqlClient">

However I have no success connecting it to an outerIP address, although the machine is connected to the internet via a router and has an outerIP address.

I'll justindicate that my GUI is supposed to be accessed via the internet (a web app) so I must be able to connecteventually via an outer IP address.

Does anybody know if I need to change some config or if it is a pure network problem.

|||

Hello

Firstly thanks for all of your replies.

Now, I've succeeded to connect my app to a remote DBbut only in my company's network, the DB is located on a different machine in the company's network and I can connect to it using this connection string:

connectionString

="Data Source=Inner network IP address \ SQLEXPRESS;Database=DBName;Uid=xxx;Pwd=yyy;"providerName="System.Data.SqlClient">

However I have no success connecting it to an outerIP address, although the machine is connected to the internet via a router and has an outerIP address.

I'll justindicate that my GUI is supposed to be accessed via the internet (a web app) so I must be able to connecteventually via an outer IP address.

Does anybody know if I need to change some config or if it is a pure network problem.

|||Hi yairt, first of all you have to make sure on teh SQL box no firewall is blocking TCP/IP communication to the SQL Express service from Internet. You can use telnet to check this, please refer to the post I mentioned in my previous post.|||

hi Iori jay

thanks for your reply.

The problem was solved (or better said was by-passed), apparently it has nothing to do with SQLSERVER or connection strings.

We connected the server to the internet via ADSL line (`and not through a router that probably concealed its address) and everything worked just fine.

Problems connecting to SQL-Server

Hi,
we have an customer trying to run our app. after installation. They get the
error messeage: Login failed for user skdomain/skuser.
Our app uses ADO.NET and the database is MS SQL Server. The program and sql
server is installed on a separate server. To run the app. they have 8
application servers with metaframe. Our app is set up to connect to the
database using WIN NT autentication.
Our app. runs fine if the user log in as domain administrator.
Is skdomain\skuser been granted access with a login in SQL Server? Do
they have the required users added to the server as well as setup as
users in the database?
-Sue
On Mon, 25 Oct 2004 08:23:03 -0700, "Olav"
<Olav@.discussions.microsoft.com> wrote:

>Hi,
>we have an customer trying to run our app. after installation. They get the
>error messeage: Login failed for user skdomain/skuser.
>Our app uses ADO.NET and the database is MS SQL Server. The program and sql
>server is installed on a separate server. To run the app. they have 8
>application servers with metaframe. Our app is set up to connect to the
>database using WIN NT autentication.
>Our app. runs fine if the user log in as domain administrator.
|||Hi Sue,
i dont follow you here. My be because i use a standalone XP Pro PC?
Where do i "click" to grant access with a login in SQL Servers? Can i see it
on my PC or must i use my customers?
Olav
"Sue Hoegemeier" wrote:

> Is skdomain\skuser been granted access with a login in SQL Server? Do
> they have the required users added to the server as well as setup as
> users in the database?
> -Sue
> On Mon, 25 Oct 2004 08:23:03 -0700, "Olav"
> <Olav@.discussions.microsoft.com> wrote:
>
>
|||You won't see skdomain\skuser on your PC. A windows login is
specific to the domain or workgroup. When using windows
authentication, any login you want to have access to SQL
Server needs to be added as a login for SQL Server. In
Enterprise Manager go to Security and then to Logins. Right
click on select New Login. Click the button to the right of
the Name text box and you will pull up the domain or
workgroup logins that you can add as logins for SQL Server.
-Sue
On Wed, 27 Oct 2004 03:37:04 -0700, "Olav"
<Olav@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Sue,
>i dont follow you here. My be because i use a standalone XP Pro PC?
>Where do i "click" to grant access with a login in SQL Servers? Can i see it
>on my PC or must i use my customers?
>Olav
>"Sue Hoegemeier" wrote:
|||Thanks Sue,
this can take som time when there is 200 users to add?
May be a faster approach is to use SQL authentication.
Then it would work with only one user registered the same place?
Is there a difference in connection speed with NT and SQL authentication?
Olav
"Sue Hoegemeier" wrote:

> You won't see skdomain\skuser on your PC. A windows login is
> specific to the domain or workgroup. When using windows
> authentication, any login you want to have access to SQL
> Server needs to be added as a login for SQL Server. In
> Enterprise Manager go to Security and then to Logins. Right
> click on select New Login. Click the button to the right of
> the Name text box and you will pull up the domain or
> workgroup logins that you can add as logins for SQL Server.
> -Sue
> On Wed, 27 Oct 2004 03:37:04 -0700, "Olav"
> <Olav@.discussions.microsoft.com> wrote:
>
>
|||When you have a lot of users, it's generally more efficient to use
Windows groups rather than individual Windows logins. Another
consideration is that you don't necessarily have to use just
Enterprise Manager to add the logins - you can execute sp_grantlogin
to grant a windows account login access to SQL Server. You can use
sp_grantdbaccess to allow the login access to a database. This can
give you more flexibility in terms of building a script the users
access.
There is no real performance difference between the two authentication
modes. Windows Authentication is more secure than using SQL logins.
You may also want to check SQL Server books online and read up on
application roles as that may be something you would want to look
into.
-Sue
On Wed, 27 Oct 2004 06:47:06 -0700, "Olav"
<Olav@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thanks Sue,
>this can take som time when there is 200 users to add?
>May be a faster approach is to use SQL authentication.
>Then it would work with only one user registered the same place?
>Is there a difference in connection speed with NT and SQL authentication?
>Olav
>
>"Sue Hoegemeier" wrote:
|||Using a single SQL Server auth login for 200 users is not very secure.
Although I'm sure the DBA will probably appreciate getting out and talking
to all 200 employees every time he decides to change that password.
Tracking down any security issues should be easier, since you don't actually
have to track 200 users; just track the one login and blame all 200 users!
"Olav" <Olav@.discussions.microsoft.com> wrote in message
news:A35FA747-EAF6-44CE-AAAB-659A6C80AB14@.microsoft.com...[vbcol=seagreen]
> Thanks Sue,
> this can take som time when there is 200 users to add?
> May be a faster approach is to use SQL authentication.
> Then it would work with only one user registered the same place?
> Is there a difference in connection speed with NT and SQL authentication?
> Olav
>
> "Sue Hoegemeier" wrote:
see it[vbcol=seagreen]
get the[vbcol=seagreen]
and sql[vbcol=seagreen]
8[vbcol=seagreen]
the[vbcol=seagreen]

Problems connecting to SQL-Server

Hi,
we have an customer trying to run our app. after installation. They get the
error messeage: Login failed for user skdomain/skuser.
Our app uses ADO.NET and the database is MS SQL Server. The program and sql
server is installed on a separate server. To run the app. they have 8
application servers with metaframe. Our app is set up to connect to the
database using WIN NT autentication.
Our app. runs fine if the user log in as domain administrator.Is skdomain\skuser been granted access with a login in SQL Server? Do
they have the required users added to the server as well as setup as
users in the database?
-Sue
On Mon, 25 Oct 2004 08:23:03 -0700, "Olav"
<Olav@.discussions.microsoft.com> wrote:

>Hi,
>we have an customer trying to run our app. after installation. They get the
>error messeage: Login failed for user skdomain/skuser.
>Our app uses ADO.NET and the database is MS SQL Server. The program and sql
>server is installed on a separate server. To run the app. they have 8
>application servers with metaframe. Our app is set up to connect to the
>database using WIN NT autentication.
>Our app. runs fine if the user log in as domain administrator.|||Hi Sue,
i dont follow you here. My be because i use a standalone XP Pro PC?
Where do i "click" to grant access with a login in SQL Servers? Can i see it
on my PC or must i use my customers?
Olav
"Sue Hoegemeier" wrote:

> Is skdomain\skuser been granted access with a login in SQL Server? Do
> they have the required users added to the server as well as setup as
> users in the database?
> -Sue
> On Mon, 25 Oct 2004 08:23:03 -0700, "Olav"
> <Olav@.discussions.microsoft.com> wrote:
>
>|||You won't see skdomain\skuser on your PC. A windows login is
specific to the domain or workgroup. When using windows
authentication, any login you want to have access to SQL
Server needs to be added as a login for SQL Server. In
Enterprise Manager go to Security and then to Logins. Right
click on select New Login. Click the button to the right of
the Name text box and you will pull up the domain or
workgroup logins that you can add as logins for SQL Server.
-Sue
On Wed, 27 Oct 2004 03:37:04 -0700, "Olav"
<Olav@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Sue,
>i dont follow you here. My be because i use a standalone XP Pro PC?
>Where do i "click" to grant access with a login in SQL Servers? Can i see i
t
>on my PC or must i use my customers?
>Olav
>"Sue Hoegemeier" wrote:
>|||Thanks Sue,
this can take som time when there is 200 users to add?
May be a faster approach is to use SQL authentication.
Then it would work with only one user registered the same place?
Is there a difference in connection speed with NT and SQL authentication?
Olav
"Sue Hoegemeier" wrote:

> You won't see skdomain\skuser on your PC. A windows login is
> specific to the domain or workgroup. When using windows
> authentication, any login you want to have access to SQL
> Server needs to be added as a login for SQL Server. In
> Enterprise Manager go to Security and then to Logins. Right
> click on select New Login. Click the button to the right of
> the Name text box and you will pull up the domain or
> workgroup logins that you can add as logins for SQL Server.
> -Sue
> On Wed, 27 Oct 2004 03:37:04 -0700, "Olav"
> <Olav@.discussions.microsoft.com> wrote:
>
>|||When you have a lot of users, it's generally more efficient to use
Windows groups rather than individual Windows logins. Another
consideration is that you don't necessarily have to use just
Enterprise Manager to add the logins - you can execute sp_grantlogin
to grant a windows account login access to SQL Server. You can use
sp_grantdbaccess to allow the login access to a database. This can
give you more flexibility in terms of building a script the users
access.
There is no real performance difference between the two authentication
modes. Windows Authentication is more secure than using SQL logins.
You may also want to check SQL Server books online and read up on
application roles as that may be something you would want to look
into.
-Sue
On Wed, 27 Oct 2004 06:47:06 -0700, "Olav"
<Olav@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thanks Sue,
>this can take som time when there is 200 users to add?
>May be a faster approach is to use SQL authentication.
>Then it would work with only one user registered the same place?
>Is there a difference in connection speed with NT and SQL authentication?
>Olav
>
>"Sue Hoegemeier" wrote:
>|||Using a single SQL Server auth login for 200 users is not very secure.
Although I'm sure the DBA will probably appreciate getting out and talking
to all 200 employees every time he decides to change that password.
Tracking down any security issues should be easier, since you don't actually
have to track 200 users; just track the one login and blame all 200 users!
"Olav" <Olav@.discussions.microsoft.com> wrote in message
news:A35FA747-EAF6-44CE-AAAB-659A6C80AB14@.microsoft.com...[vbcol=seagreen]
> Thanks Sue,
> this can take som time when there is 200 users to add?
> May be a faster approach is to use SQL authentication.
> Then it would work with only one user registered the same place?
> Is there a difference in connection speed with NT and SQL authentication?
> Olav
>
> "Sue Hoegemeier" wrote:
>
see it[vbcol=seagreen]
get the[vbcol=seagreen]
and sql[vbcol=seagreen]
8[vbcol=seagreen]
the[vbcol=seagreen]

Problems backing up SQL Express Database...

Hello,

I found some code below that works fine when I run it in my vb.net code in Design mode. When I publish the application, run the app and then execute the sub MyDbBackup() I get the following error: Cannot open backup device 'C:\dbBackup'. Operating system error 5(Access is denied). BACKUP DATABASE is terminating abnormally.

Here is the code that runs:

Public Sub MyDbBackup()
Dim sqlconn As New SqlClient.SqlConnection(MyConnectionStringdb)
sqlconn.Open()
Dim Backupcommand As SqlClient.SqlCommand = New SqlClient.SqlCommand("BACKUP DATABASE [" & sqlconn.Database.ToString & "] TO DISK = 'c:\myDataBaseBackup.bak'")
Backupcommand.CommandType = CommandType.Text
Backupcommand.Connection = sqlconn
Backupcommand.ExecuteNonQuery()
sqlconn.Close()
End Sub

2 Questions: Why does it backup fine in design mode, but not after it is published? Also, in design mode, my database is called TAP_Master.mdf but when I look under C:\Program Files\Microsoft\ SQL Server\MSSQL.1\MSSQL\Data, I do not see that database name... all I see is master.mdf, model, msdbdata etc... Is that database stored anywhere else?

I have set the MyConnectionStringdb variable to = "Data Source =.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\TAP_Master.mdf;Integrated Security=True;User Instance=True"

Thanks in advance.

You don't see your database in the Data directory because you embedded it in your application. The database is installed to the same location where you application is installed, which is an obfuscated path that is generated during ClickOnce installation. ClickOnce applications use a special type of instances of SQL Server called a User Instance to allow the database to be attached at runtime.

I'm not sure about the backup failure, I'll have to do a little more research. Is your published application on a different computer than the Dev box? I'm thinking it has something to do with a backup device that was created on the Dev box, but does not exist on the test box.

Mike

|||

Mike Wachal - MSFT wrote:

You don't see your database in the Data directory because you embedded it in your application. The database is installed to the same location where you application is installed, which is an obfuscated path that is generated during ClickOnce installation. ClickOnce applications use a special type of instances of SQL Server called a User Instance to allow the database to be attached at runtime.

I'm not sure about the backup failure, I'll have to do a little more research. Is your published application on a different computer than the Dev box? I'm thinking it has something to do with a backup device that was created on the Dev box, but does not exist on the test box.

Mike

Thanks for your reply. You are correct... My published application is on a different computer than my Dev box. If you can find out any additional info as to why I'm getting that error that would be great.

Also, I'll ask this question as well, Once the bak up file is created, what would be the best method to restore the .bak file to the machine that runs the published application.? I thought I could use the following code, but I receive the message, "Restore cannot process the database C"\Visual Studio\Projects\Prog\BIN\DEBUG\TAP_Master.MDF beause it is in use by this session. It is recommended that the master database be used when performing this operation":

Public Sub MyDbBackup()
Dim sqlconn As New SqlClient.SqlConnection(MyConnectionStringdb)
sqlconn.Open()
Dim Backupcommand As SqlClient.SqlCommand = New SqlClient.SqlCommand("RESTORE DATABASE [" & sqlconn.Database.ToString & "] FROM DISK = 'c:\myDataBaseBackup.bak'")
Backupcommand.CommandType = CommandType.Text
Backupcommand.Connection = sqlconn
Backupcommand.ExecuteNonQuery()
sqlconn.Close()
End Sub

Thanks in advance.

|||

Hi,

I guess that the user instance feature is not made for Backup and restore (with the emphasize on restore) because a restore will do a server attaching after the restoring which is not the sense of a user attached instance. Why don′t you take the MDF as a backup only ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Jens K. Suessmeyer wrote:

Hi,

... Why don′t you take the MDF as a backup only ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Hello, can you elaborate on that quote? How can I take only the MDF as a backup? Basically I want to be able to back up any saved data, and then be able to restore it in case of a system failure or a corrupted operating system.

Thanks for your replies all.

|||Just do a normal file copy when the database connection is closed, then you can easily attach it to a user instance again when the data is corrupt.

HTH, Jens K. Suessmeyer.

htttp://www.sqlserver2005.de

|||

Ok. This is what I have done. I opened my published app on my laptop, and then entered in some data. I closed my app, and then attempted to copy the master.mdf file from the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data directory. At first I couldn't copy because SQL server express was still running. So I killed the services and copied the data.

I reinstalled my app, copied back the master.mdf into the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data directory, and then launched the app. Now I do not see the data that I previously entered.

Am I understanding the File Copy / Attach to user instance concept correctly?

Thanks again for all your help.

|||No actually not, the database which has to be backup is your own database not the SQL Server internal ones. YOu will have to backup the MDF file of the database with the reference TAP_master.mdf you mentioned above.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

The reason you're seeing the backup error is that the user context running your app on the deployed system doesn't have Windows permissions to create a file in the root of the local C: drive. That's why it's different from your dev environment: Different machine, different permissions.

So, either point the backup to a known directory that you're guaranteed to have permission to write to on machines where you're deployed, or find a way to make sure that you have appropriate permissions to the root of C:.

On the restore, it's simply a matter that you can't overwrite a database while you have an active session attached to it. Your connection is that session. By setting focus to Master (use master) you're taking focus away from the database you're trying to restore, and it should work fine.

|||

Kevin Farlee wrote:

On the restore, it's simply a matter that you can't overwrite a database while you have an active session attached to it. Your connection is that session. By setting focus to Master (use master) you're taking focus away from the database you're trying to restore, and it should work fine.

Ok thanks...First issue resolved... Now with regards to the second issue, Where am I setting focus to the master from? Is it within Visual Studio design mode, or under SQL Server 2005 Surface Area Configuration?

Thanks.

|||

Rashar wrote:

Kevin Farlee wrote:

On the restore, it's simply a matter that you can't overwrite a database while you have an active session attached to it. Your connection is that session. By setting focus to Master (use master) you're taking focus away from the database you're trying to restore, and it should work fine.

Ok thanks...First issue resolved... Now with regards to the second issue, Where am I setting focus to the master from? Is it within Visual Studio design mode, or under SQL Server 2005 Surface Area Configuration?

Thanks.

The context information is session based, you can change the context from within your script (if you are using one, I am not sure from your explnation using the USE <DatabaseName> command. If you are in any GUI of SQL Management Studio, make sure that you are not residing on a database node in the treeview that you want to restore.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Problem with WHERE clause when column length > 255

Hello, I am using the JDCB-ODBC driver for my app, but one of the columns in my WHERE clause is 255 characters long. Because of this no rows are returned even though the statement should return 1 or 2 rows. I've tried other JDBC-ODBC drivers too and they have the same problem. Additionally, I've tried using RTrim(), Substring(), etc and it still will not work...any ideas? Is it a driver bug? Anyone know of a driver that will work?

Sample code...

ResultSet rs = dbRetrieve.getStatement().executeQuery( sql ) ;
if (rs.next()) {
// Never gets here
}

Thanx!Have you run the query (verbatim) in Microsoft Query Analyzer and seen the rows returned?

-PatP|||Originally posted by Pat Phelan
Have you run the query (verbatim) in Microsoft Query Analyzer and seen the rows returned?

-PatP

Yes, I have and it returns results. Additionally, I've removed the column from the where clause in my java file and it returns data, but of course its uselys because I need that column in the where clause...

Thanks...|||Hmm... Microsoft's JDBC driver says it will support upt to 4000 character strings. Have you used profiler to see exactly what's being sent to your SQL server?|||Since the SQL code works ok from Query Analyzer, we can assume that SQL Server to the MDAC on your client works fine. The problem must be in the JDBC driver or beyond it.

Which JDBC driver are you using? Does it have any length limitations that you are aware of (or does it keep them as surprises for the unwary)? As Peter pointed out, the Microsoft JDBC driver handles big strings (I've run 2 Kb columns out through it).

Just as another thought, are you certain that your Java app is behaving and actually submitting what you expect it to.

-PatP

Problem with VB6 App & SQL 2000 (Locking & lost transactions)

Problem with VB6 App & SQL 2000 (Locking & lost transactions)
Hi,
We are having a big, big problem with our OLTP system.
We have a VB6 App. that receive transactions (TX) via Winsock from an
Access Server (NAC) that comes from Points-of-sales (POS)
The VB 6 App receive the packet, then pharses it and fill a lot of variable.
Then the App call a stored procedure (With ADO) called t_recepcion whith
aprox. 10 parameters (That are form the pharse proccess) and the sp receive
the results as output parameters. Finally the App build the response packet
and send it to the POS by Winsock Again.
This sp (t_recepcion) call another sp for resolve the transaction.
There are 15000 transactions per day
Well, the problem is that we are losing transactions from the database that
were responded by the system (The people that
made the transaction had the ticket printed)
I don´t know how can I make the BEGIN - COMMIT for have the highest
isolation level for each transaction. or if I must change something in the
SQL Engine
When one transaction come to the App and hang, the App continue responding
transactions but in some cases I must close the App. Then the system make a
ROLLBACK to this hanged transaction (Losing the transactions that were
responsed after the hang)
I don´t know if you understand my problem (My English is not good, and I am
not the developer)
But I need to solve this tremendous problem
If you could solve it , you are very welcome. if not, tell me if you have
some tips for do this
Thanks in Advance
Javier
mask@.impsat1.com.arPlease take a look at these articles for more info:
http://support.microsoft.com/default.aspx?scid=kb;en-us;323630
http://support.microsoft.com/default.aspx?scid=kb;en-us;75722
http://support.microsoft.com/default.aspx?scid=kb;en-us;295108
http://support.microsoft.com/default.aspx?scid=kb;en-us;224453
--
-oj
RAC v2.1 & QALite!
http://www.rac4sql.net
"Javier Villegas" <mask@.impsat1.com.ar> wrote in message
news:yO6ha.81744$rJ3.35069@.fe10.atl2.webusenet.com...
> Problem with VB6 App & SQL 2000 (Locking & lost transactions)
> Hi,
> We are having a big, big problem with our OLTP system.
> We have a VB6 App. that receive transactions (TX) via Winsock from an
> Access Server (NAC) that comes from Points-of-sales (POS)
>
> The VB 6 App receive the packet, then pharses it and fill a lot of
variable.
> Then the App call a stored procedure (With ADO) called t_recepcion whith
> aprox. 10 parameters (That are form the pharse proccess) and the sp
receive
> the results as output parameters. Finally the App build the response
packet
> and send it to the POS by Winsock Again.
> This sp (t_recepcion) call another sp for resolve the transaction.
> There are 15000 transactions per day
> Well, the problem is that we are losing transactions from the database
that
> were responded by the system (The people that
> made the transaction had the ticket printed)
> I don´t know how can I make the BEGIN - COMMIT for have the highest
> isolation level for each transaction. or if I must change something in the
> SQL Engine
> When one transaction come to the App and hang, the App continue responding
> transactions but in some cases I must close the App. Then the system make
a
> ROLLBACK to this hanged transaction (Losing the transactions that were
> responsed after the hang)
> I don´t know if you understand my problem (My English is not good, and I
am
> not the developer)
> But I need to solve this tremendous problem
> If you could solve it , you are very welcome. if not, tell me if you have
> some tips for do this
> Thanks in Advance
> Javier
> mask@.impsat1.com.ar
>
>
>
>