I have a crystal report using with vb6. When I export to excel, it is automatically erasing in 2 seconds. Means when I click export excel save as windows is opening and saving in selected location but within 2 to 3 seconds it is deleting automatically. I have tried in many systems. But all other reports are working fine. Kindly help me out. What could be the reason?
I don't the problem why it happened like that. What actually happened is we've migrated Oracle db from 9i to 11g. After migration some of the reports are unable to export which I've mentioned in issue.
I've opened the report and given db user, password and schema (Which already is there) and saved again. Now working fine.
Related
After installing Oracle 12c database, Weblogic and forms.
I added button on blank form to show message or execute query.
In the runtime the when_button_pressed not work but if I press Ctrl+F11 it executes well.
Not that I move fmx file from Windows machine to Linux machine where weblogic and database are installed.
If you really named the trigger when_button_pressed, then this is the reason. Triggers - which are built-in into Forms - have a hyphen, not an underline, i.e. when-button-pressed is its correct name.
If this is not the case (but a matter of a typo), posting trigger code might help. What does it contain?
Suddenly SQL worksheet is not displaying in my SQL Developer. When I click on 'Open SQL Worksheet' or Alt+F10 nothing will appear.
I have tried many things such as: uninstalling SQL developer; cleaned the appData; changing java version; change SQL Developer version; and so on. But nothing has worked. Help?
Try to open Sql Developer as administrator. It's weird but works for me.
While any the software - SQLDeveloper got error or something worng.
You can try to
backup whole sqldeveloper directory from C:\Users\AppData\Roaming\
then delete it.
But remember to backup your customer infomation!
Or reference this SQLDeveloper not starting
Hope this can help.
I clear folder C:\Users\AppData\Roaming\SQL Developer\SqlHistory. It works for me.
For me, it was path problem. I changed path of temp and TMP in environment variable to C:\Users\____\Appdata\Local\Temp
Then worksheet showed up again. somehow I changed this path before, that was the reason for me.
I was able to solve this by :
Closing SQL developer
Deleting the file SqlHistory.xml that is located at C:\Users\AppData\Roaming\SQL Developer\. Alternatively, you can rename it to e.g SqlHistoryOLD.xml
Now when you open SQL developer and create a new SQL worksheet, it will work :)
Here is in interesting one.
I have a Crystal Report that uses a single Microsoft Access 2007 table. The data in the table is updated at run time based on criteria from a list box.
If I select one entry from my list it updates the data and shows in the report. If I select and different entry is shows the data the old data. If i select that report enough times it will eventually show the new data.
The data in the access data base is updated as I checked manually
My problem is that there seems to be a delay in between the data updating and the report showing the new data.
Is there anyway to reduce this delay or get my program to wait until access has finished updating ?
Here's some ideas:
If you're mixing cr-xi with VS2010, and have no real reason to do so, then uninstall xi and install the new libraries for VS2010. I had issues mixing cr-xi with VS2010.
There's an option to save data with report. Make sure that's turned off. If it already was, turn it on, run the report, then turn it off again.
You can try rpt.Refresh(), right before crystalReportViewer1.ReportSource = rpt.
This page had some ideas, including the last one I listed.
Update
I've just found what's causing it but couldn't solve it :
When running the project, VS copies the SDF file to bin\Debug, therefore, any changes made to it, even if only refreshing the DB will cause it to be overwritten...
I've created a quick and dirty project to test SQL CE 4.0, designed a small table and added an Update button to save entered data. So far everything works, I close and reopen the application, data is loaded and shown in the DataGridView.
There is one issue however, whenever I make any changes in Server Explorer such as just refreshing the connection,
when I launch the application again, all the data I entered is gone.
Did I miss something ?
How I created the database :
From Data Sources I've added a new data source, created a new connection, created a new database, answered yes for copying it to my project and modifying the connection.
Then from Server Explorer I created a new table, added columns
Finally, I reconfigured my data source so it recreates the data set, data table and the adapter
Here is a fix for it :
Do not copy it locally to the project folder, there won't be two versions with one overwriting the other.
for whom using QTP(Quick Test Professional) do anyone of you face this issue on data table upon savin script on QC(Quality Center).
When you try to edit "DataTable" message box says that "locked cells cannot modified" displays.
kindly see the attached snapshot.
your help and support is highly appreciated.
Thanks,
Manaysah
I have found that the following procedure corrects this problem:
Open the test in QTP
Check it out
Right-click the datatable
Select File > Export…
Browse to the location where you want to save the export file
Enter a file name for the export file
Click Save
Right-click the datatable
Select File > Import
Browse to the location where you saved the export file
Select the export file
Click OK
Datatable should now be unlocked.
If you are using QC 10.0 to store/save your QTP 10.0 scripts ,then you can try following.
Verify what patch level your QC 10.o on if you are on patch 28 then you have to apply patch 29 on QC.
Defect ID: QCCR1J 24598
Problem: An automatic job runs every fifteen minutes that cleans the database of stale sessions and locks.
A regression prevents locks from being deleted if the Quality Center client was terminated abruptly.
This causes entities to remain locked even after the LOCK_TIMEOUT and the entities cannot be edited.
A workaround existed to physically delete the locked rows from the database