Flash inside a report

Is it possible to show flash inside a report. I would like to call my report
which calls a php-Script that shows a flash animation. Then it would be
possible to use animatet charts like php/swf chart from http://www.maani.us.
psychodad
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200610/1No, this is not possible. Remember, this product is designed to render in
multiple formats (html, excel, pdf, csv, etc). Flash is really not
compatible with that sort of design.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"psychodad71" <u2248@.uwe> wrote in message news:674116628bee0@.uwe...
> Is it possible to show flash inside a report. I would like to call my
> report
> which calls a php-Script that shows a flash animation. Then it would be
> possible to use animatet charts like php/swf chart from
> http://www.maani.us.
> psychodad
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200610/1
>sql

Flagging duplicate records (again)

Hi to all and thanks for the replys, but i'm still having a problem. What i
need to do is set dupe = 1 for all records where the phone call (by date) is
less than 30 days from the previous one (having the same phone number). For
example:
call_date phone_no dupe
2005-08-30 13:39:00 888-888-8888 0
2005-08-30 13:41:00 888-888-8888 1
2005-12-12 15:23:00 888-888-8888 0
2005-12-15 07:54:00 888-888-8888 1
Thanks to all in advance. It seems easy but i can't seem to figure it outThe first time you posted this question you haven't provided DDL and sample
data, and you weren't happy with the answers. Are you going for a second tim
e?
Maybe you should read this (if you haven't already):
http://www.aspfaq.com/etiquette.asp?id=5006
ML
http://milambda.blogspot.com/

Fix for transmission_status message Connection handshake failed [...] The logon attempt failed

Full message:

Connection handshake failed. An OS call failed: (8009030c) 0x8009030c(The logon attempt failed). State 66

Under these conditions, setting trustworthy on on the sending and receiving databases will solve this issue

1) Communicating between multiple instances

2) Using Kerberos security (NT Authentication, i.e. not certificates)

The problem is from the SQL service account (the Windows account that runs the SQL Server instance service). It may be that the password has expired, the service account is missing the needed priviledges over the SPN in the Active Directory or the SPN is missing completely.

First connection timeout when using full text indexing

After rebooting the computer (anytime), the first call to the database will almost always time out. This did not happen prior to adding the full text index to the database. It will time out even in the SQL Express Management Suite.

After that first time out, it works fine.

We tried a workaround by making our first call to the database a "dummy" call and wrapping it in a try/catch.

That didn't work either. Any suggestions?

Regards,

Pat

Someone suggested that your issue may be described in the KB, check it out here.

Mike

|||

The article you referred to is about querying the database. However, our problem is at connection time. When the appliction try to start a connection to the database after the SQL server machine reboot, it always timeout. We then try to make the connection again and it always works!

First of all, we didn't have this problem before we add Full-Text index to our database. The happens ONLY with SQL Express with the default security setup, which means the SQL Express instance is owned by "Network Services". When we make "Local System" to be the owner of the SQL Express instance, the problem goes away. This problem also NEVER happens on a server running the Full SQL Server version which default to use "Local System".

We could not find a way to default SQL Express to run on "Local System". If anyone knows of a way to do this, it will solve our problem too.

|||

Mike Wachal - MSFT wrote:

Someone suggested that your issue may be described in the KB, check it out here.

Mike

Thank you for your help, I solved my problem with sp_fulltext_service 'verify_signature', 0;

First connection timeout when using full text indexing

After rebooting the computer (anytime), the first call to the database will almost always time out. This did not happen prior to adding the full text index to the database. It will time out even in the SQL Express Management Suite.

After that first time out, it works fine.

We tried a workaround by making our first call to the database a "dummy" call and wrapping it in a try/catch.

That didn't work either. Any suggestions?

Regards,

Pat

Someone suggested that your issue may be described in the KB, check it out here.

Mike

|||

The article you referred to is about querying the database. However, our problem is at connection time. When the appliction try to start a connection to the database after the SQL server machine reboot, it always timeout. We then try to make the connection again and it always works!

First of all, we didn't have this problem before we add Full-Text index to our database. The happens ONLY with SQL Express with the default security setup, which means the SQL Express instance is owned by "Network Services". When we make "Local System" to be the owner of the SQL Express instance, the problem goes away. This problem also NEVER happens on a server running the Full SQL Server version which default to use "Local System".

We could not find a way to default SQL Express to run on "Local System". If anyone knows of a way to do this, it will solve our problem too.

|||

Mike Wachal - MSFT wrote:

Someone suggested that your issue may be described in the KB, check it out here.

Mike

Thank you for your help, I solved my problem with sp_fulltext_service 'verify_signature', 0;

First connection timeout when using full text indexing

After rebooting the computer (anytime), the first call to the database will almost always time out. This did not happen prior to adding the full text index to the database. It will time out even in the SQL Express Management Suite.

After that first time out, it works fine.

We tried a workaround by making our first call to the database a "dummy" call and wrapping it in a try/catch.

That didn't work either. Any suggestions?

Regards,

Pat

Someone suggested that your issue may be described in the KB, check it out here.

Mike

|||

The article you referred to is about querying the database. However, our problem is at connection time. When the appliction try to start a connection to the database after the SQL server machine reboot, it always timeout. We then try to make the connection again and it always works!

First of all, we didn't have this problem before we add Full-Text index to our database. The happens ONLY with SQL Express with the default security setup, which means the SQL Express instance is owned by "Network Services". When we make "Local System" to be the owner of the SQL Express instance, the problem goes away. This problem also NEVER happens on a server running the Full SQL Server version which default to use "Local System".

We could not find a way to default SQL Express to run on "Local System". If anyone knows of a way to do this, it will solve our problem too.

|||

Mike Wachal - MSFT wrote:

Someone suggested that your issue may be described in the KB, check it out here.

Mike

Thank you for your help, I solved my problem with sp_fulltext_service 'verify_signature', 0;