Hai Friends,
I am using Crystal Report 9.2.
In my project, i am in need of finding the Subtotal, totals.
While doing so, its assigning the value as 2,234,456.00
i am in need of that display to be 22,34,456.00.
i tried for Formula Field & also Selection Formula's Group in Crystal Report.
In the Format Field, i am not able to customize for thousand.
Can any one help me to solve my problem for finding the total.Interesting question. I don't think you can do this easily. You might have to create a new formula field and use string manipulation.|||Hai Babu - Moderator,
Are u there? Why no reply from u?
Regards
Geetha|||hai Moderator,
What happened to u?
why u r not responding.
in crystal report as well as in access, we have this type of display for the totals.
rectify this.
Regards
geetha|||Convert the money to text and seperate the digits according to the format you want and combine them by ","
Showing posts with label project. Show all posts
Showing posts with label project. Show all posts
Friday, March 30, 2012
Monday, March 26, 2012
How to fix SQLExpress "attempt to attach an auto-named database" e
I'm authoring a .net webservice that connects to a SQLExpress database in the
same project. When the code calls the database the following exception is
thrown:
"An attempt to attach an auto-named database for file
C:\[...]\App_Data\App_Data\MyDatabase.mdf failed. A database with the same
name exists, or specified file cannot be opened, or it is located on UNC
share."
I've read all the online help I can find but none of the suggestions work.
* I've deleted the SQLExpress folder in my ApplicationData
* I've made sure to enable user instances in the server and RECONFIGURE
* I've restarted the service
* I've ensured that ASPNET and NETWORK SERVICE has rights to the APP_DATA
folder.
Nothing changes. What is the cause of this issue' How can I fix it'
Thanks,
JasonSolved.
It took finally writing this post to see that the rendered connection string
renders "APP_DATA" twice.
This is how the project defaults - I didn't do that. Screw them.
Jason
"Jason" wrote:
> I'm authoring a .net webservice that connects to a SQLExpress database in the
> same project. When the code calls the database the following exception is
> thrown:
> "An attempt to attach an auto-named database for file
> C:\[...]\App_Data\App_Data\MyDatabase.mdf failed. A database with the same
> name exists, or specified file cannot be opened, or it is located on UNC
> share."
> I've read all the online help I can find but none of the suggestions work.
> * I've deleted the SQLExpress folder in my ApplicationData
> * I've made sure to enable user instances in the server and RECONFIGURE
> * I've restarted the service
> * I've ensured that ASPNET and NETWORK SERVICE has rights to the APP_DATA
> folder.
> Nothing changes. What is the cause of this issue' How can I fix it'
> Thanks,
> Jason|||Congratulations!
Have a great day!
Charles Wang
Microsoft Online Community Support|||But it still doesn't work right. After the change, it will not have that
error in run-time, but now it won't work in design-time. The DataSet
visualizer can't find the datasource from the given connectionString.
This is using the Application project template for WebService and not the
Website template. That may be part of the problem.
Jason
"Charles Wang[MSFT]" wrote:
> Congratulations!
> Have a great day!
> Charles Wang
> Microsoft Online Community Support
>|||Hi Jason,
Thanks for your response.
I recommend that you try to connect the SQL Server Express on other clients
via SQL Query Analyzer or other SQL client tools. If you manage to access
the server, this issue is most likely caused by some settings in your
Webservice IDE (vs.net 2005?). You can post this issue to .net public
community for best support.
Also, for now, I recommend that you check your connection string, by
default the SQLExpress instance name should be set to "<server
name>\SQLEXPRESS".
You may want these references:
http://blog.davebouwman.net/2006/03/27/SQLExpressConnectionProblems.aspx
http://msdn.microsoft.com/vbrun/vbfusion/usingsqlexpress/
http://www.connectionstrings.com/
Charles Wang
Microsoft Online Community Support|||Hi ,
Just checking in to see if the suggestions were helpful. Please let us know
if you would like further assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support|||Charles,
Thanks, but no. Those suggestions seem to address a different issue. I
think what's happening here is that when using the non-website project
template for ASP.Net Webservice (downloaded from Microsoft's site) the
connection string contains an extra "APP_DATA" directory literal.
At design time, this is the correct setting and the dataset designers can
find and connect to the database correctly, but at runtime the "APP_DATA"
literal is /extra/ because the "|DataDirectory|" placeholder is resolved
differently to already include the APP_DATA folder.
I'm posting these findings to save others from frustration, but I've in fact
changed direction.
Jason
"Charles Wang[MSFT]" wrote:
> Hi ,
> Just checking in to see if the suggestions were helpful. Please let us know
> if you would like further assistance.
> Have a great day!
> Charles Wang
> Microsoft Online Community Support
>|||Hi Jason,
Appreciate your posting here for having others benefit from this issue.
My former reply may not understand your issue clearly. I thought it was
just a normal SQL Server break/fix issue on connection.
This issue is most likely a .net development issue.I recommend that you
post this issue to public .net newsgroups for best professional support.
If you also want to get support on this newsgroup, I would like to get a
simple project example from you so that I can try to reproduce this issue
for further research.
Sincerely yours,
Charles Wang
Microsoft Online Community Support|||I just had the same problem. I noticed that Permissions on APP_DATA
were not being inherited by the .mdf and .ldf files. Made sure ASPNET
had permission to folder then changed to inherit permissions and all
works OK. Don't know security issues but this is a development site so
don't care.
same project. When the code calls the database the following exception is
thrown:
"An attempt to attach an auto-named database for file
C:\[...]\App_Data\App_Data\MyDatabase.mdf failed. A database with the same
name exists, or specified file cannot be opened, or it is located on UNC
share."
I've read all the online help I can find but none of the suggestions work.
* I've deleted the SQLExpress folder in my ApplicationData
* I've made sure to enable user instances in the server and RECONFIGURE
* I've restarted the service
* I've ensured that ASPNET and NETWORK SERVICE has rights to the APP_DATA
folder.
Nothing changes. What is the cause of this issue' How can I fix it'
Thanks,
JasonSolved.
It took finally writing this post to see that the rendered connection string
renders "APP_DATA" twice.
This is how the project defaults - I didn't do that. Screw them.
Jason
"Jason" wrote:
> I'm authoring a .net webservice that connects to a SQLExpress database in the
> same project. When the code calls the database the following exception is
> thrown:
> "An attempt to attach an auto-named database for file
> C:\[...]\App_Data\App_Data\MyDatabase.mdf failed. A database with the same
> name exists, or specified file cannot be opened, or it is located on UNC
> share."
> I've read all the online help I can find but none of the suggestions work.
> * I've deleted the SQLExpress folder in my ApplicationData
> * I've made sure to enable user instances in the server and RECONFIGURE
> * I've restarted the service
> * I've ensured that ASPNET and NETWORK SERVICE has rights to the APP_DATA
> folder.
> Nothing changes. What is the cause of this issue' How can I fix it'
> Thanks,
> Jason|||Congratulations!
Have a great day!
Charles Wang
Microsoft Online Community Support|||But it still doesn't work right. After the change, it will not have that
error in run-time, but now it won't work in design-time. The DataSet
visualizer can't find the datasource from the given connectionString.
This is using the Application project template for WebService and not the
Website template. That may be part of the problem.
Jason
"Charles Wang[MSFT]" wrote:
> Congratulations!
> Have a great day!
> Charles Wang
> Microsoft Online Community Support
>|||Hi Jason,
Thanks for your response.
I recommend that you try to connect the SQL Server Express on other clients
via SQL Query Analyzer or other SQL client tools. If you manage to access
the server, this issue is most likely caused by some settings in your
Webservice IDE (vs.net 2005?). You can post this issue to .net public
community for best support.
Also, for now, I recommend that you check your connection string, by
default the SQLExpress instance name should be set to "<server
name>\SQLEXPRESS".
You may want these references:
http://blog.davebouwman.net/2006/03/27/SQLExpressConnectionProblems.aspx
http://msdn.microsoft.com/vbrun/vbfusion/usingsqlexpress/
http://www.connectionstrings.com/
Charles Wang
Microsoft Online Community Support|||Hi ,
Just checking in to see if the suggestions were helpful. Please let us know
if you would like further assistance.
Have a great day!
Charles Wang
Microsoft Online Community Support|||Charles,
Thanks, but no. Those suggestions seem to address a different issue. I
think what's happening here is that when using the non-website project
template for ASP.Net Webservice (downloaded from Microsoft's site) the
connection string contains an extra "APP_DATA" directory literal.
At design time, this is the correct setting and the dataset designers can
find and connect to the database correctly, but at runtime the "APP_DATA"
literal is /extra/ because the "|DataDirectory|" placeholder is resolved
differently to already include the APP_DATA folder.
I'm posting these findings to save others from frustration, but I've in fact
changed direction.
Jason
"Charles Wang[MSFT]" wrote:
> Hi ,
> Just checking in to see if the suggestions were helpful. Please let us know
> if you would like further assistance.
> Have a great day!
> Charles Wang
> Microsoft Online Community Support
>|||Hi Jason,
Appreciate your posting here for having others benefit from this issue.
My former reply may not understand your issue clearly. I thought it was
just a normal SQL Server break/fix issue on connection.
This issue is most likely a .net development issue.I recommend that you
post this issue to public .net newsgroups for best professional support.
If you also want to get support on this newsgroup, I would like to get a
simple project example from you so that I can try to reproduce this issue
for further research.
Sincerely yours,
Charles Wang
Microsoft Online Community Support|||I just had the same problem. I noticed that Permissions on APP_DATA
were not being inherited by the .mdf and .ldf files. Made sure ASPNET
had permission to folder then changed to inherit permissions and all
works OK. Don't know security issues but this is a development site so
don't care.
How to fix SQLExpress "attempt to attach an auto-named database" e
I'm authoring a .net webservice that connects to a SQLExpress database in th
e
same project. When the code calls the database the following exception is
thrown:
"An attempt to attach an auto-named database for file
C:\[...]\App_Data\App_Data\MyDatabase.mdf failed. A database with the sa
me
name exists, or specified file cannot be opened, or it is located on UNC
share."
I've read all the online help I can find but none of the suggestions work.
* I've deleted the SQLExpress folder in my ApplicationData
* I've made sure to enable user instances in the server and RECONFIGURE
* I've restarted the service
* I've ensured that ASPNET and NETWORK SERVICE has rights to the APP_DATA
folder.
Nothing changes. What is the cause of this issue' How can I fix it'
Thanks,
JasonSolved.
It took finally writing this post to see that the rendered connection string
renders "APP_DATA" twice.
This is how the project defaults - I didn't do that. Screw them.
Jason
"Jason" wrote:
> I'm authoring a .net webservice that connects to a SQLExpress database in
the
> same project. When the code calls the database the following exception is
> thrown:
> "An attempt to attach an auto-named database for file
> C:\[...]\App_Data\App_Data\MyDatabase.mdf failed. A database with the
same
> name exists, or specified file cannot be opened, or it is located on UNC
> share."
> I've read all the online help I can find but none of the suggestions work.
> * I've deleted the SQLExpress folder in my ApplicationData
> * I've made sure to enable user instances in the server and RECONFIGURE
> * I've restarted the service
> * I've ensured that ASPNET and NETWORK SERVICE has rights to the APP_DATA
> folder.
> Nothing changes. What is the cause of this issue' How can I fix it'
> Thanks,
> Jason|||Congratulations!
Have a great day!
Charles Wang
Microsoft Online Community Support
e
same project. When the code calls the database the following exception is
thrown:
"An attempt to attach an auto-named database for file
C:\[...]\App_Data\App_Data\MyDatabase.mdf failed. A database with the sa
me
name exists, or specified file cannot be opened, or it is located on UNC
share."
I've read all the online help I can find but none of the suggestions work.
* I've deleted the SQLExpress folder in my ApplicationData
* I've made sure to enable user instances in the server and RECONFIGURE
* I've restarted the service
* I've ensured that ASPNET and NETWORK SERVICE has rights to the APP_DATA
folder.
Nothing changes. What is the cause of this issue' How can I fix it'
Thanks,
JasonSolved.
It took finally writing this post to see that the rendered connection string
renders "APP_DATA" twice.
This is how the project defaults - I didn't do that. Screw them.
Jason
"Jason" wrote:
> I'm authoring a .net webservice that connects to a SQLExpress database in
the
> same project. When the code calls the database the following exception is
> thrown:
> "An attempt to attach an auto-named database for file
> C:\[...]\App_Data\App_Data\MyDatabase.mdf failed. A database with the
same
> name exists, or specified file cannot be opened, or it is located on UNC
> share."
> I've read all the online help I can find but none of the suggestions work.
> * I've deleted the SQLExpress folder in my ApplicationData
> * I've made sure to enable user instances in the server and RECONFIGURE
> * I've restarted the service
> * I've ensured that ASPNET and NETWORK SERVICE has rights to the APP_DATA
> folder.
> Nothing changes. What is the cause of this issue' How can I fix it'
> Thanks,
> Jason|||Congratulations!
Have a great day!
Charles Wang
Microsoft Online Community Support
Wednesday, March 7, 2012
How to Find Full Text Index Catalog Creation - Time duration.
I Have used full text indexin my project.
I want to find "Full Text Index Catalog Creation" Time duration.
Is there any method to find.
I am using SQL Server 2005
Regards
Vasanth Thangasamy
The start and stop times are logged in the event log. I believe the stop time includes the duration but not sure without checking.Friday, February 24, 2012
how to find data mining 's example
how to find data mining 's example from sql2005
how to apply data mining in project
This might be a good starting point...
http://msdn2.microsoft.com/en-us/library/ms175595(SQL.90).aspx
|||There is a Data Mining forum and I am sure you will find relevant information there.
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=81&SiteID=1
Sunday, February 19, 2012
How to Finalize my SSIS project
Do I need to convert my SSIS project in VS and deploy it first somehow on my server?
I know that an SSIS project creates a package.dtsx by default so do I need to publish this so that I can see it in SQL Server Management Studio under my Integration Services section? I do not see any packages and get an error when trying to click on the folders "filesystem" or "MDSB" under my SSIS connection in Server Management Studio....likewise when I try creating a job, I try to browse to packages and get a cryptic error, probably because my package isn't showing up in Server Management Studio yet.
The error I get while trying to import packages is saying it can't enumerate or something when I try to browse to my package location. I also get an error saying "encryption not supported on SQL Server (Microsoft Native client) when trying to browse to my package location when trying to import my package in SSIS in Server Management Studio.
Two (different) answers:
1) You don't have to do anything, you can just copy .dtsx file to the server and run it using DTEXEC command line, or schedule it using Agent directly from the file system. While running, it will appear in SSMS 'Running Packages' node, but it will not be in 'Stored Packages' node since it is not stored in SSIS Server.
2) If you want package to appear in 'Stored Packages' in SSMS, you do need to deploy them to the server. Several options exists how to do this: Save Copy As.. command in VS, deployment wizard, dtutil.exe tool. See BOL for more info.
|||Thanks a lot!
Subscribe to:
Posts (Atom)