I am doing analysis in Contour using the older version of the data. Now, I want to save the result as dataset but saving data with "Save as dataset" button saves latest version of the data. Please suggest how I save the result with older version.
Related
Im getting this error when running an SSIS project that moves all of our files from FoxPro into SSMS Dbs. The corresponding DBF file opens fine on FoxPro and the memo field which is the FPT file to knowledge works fine too, So I don't what the solution is, I tried making a little changes to the memos to see if that would update the file but that didnt work. I tired re indexing the DBF but no luck there either. How can i generate a new FPT file so I can run this project. How could it be invalid. There is no support online for this.
You are using a third party .NET tool (RatSql.DbfReader). Judging from the exception message this tool was written in a .NET language. It's not a Microsoft product and not part of Visual FoxPro.
DBF files are a family of formats that are similar but have subtle differences. Many tools that claim to support DBF files, will only support DBF files created by certain products, such as VFP 6, FP 2.6, dBase or Clipper.
The options I see for you:
Get in contact with the vendor and make sure that Visual FoxPro tables are supported by their product. They might have an update or can suggest alternative solutions.
If this is an in-house developed product you need to get into touch with the original developers.
Since you have Visual FoxPro, you can convert the file to an older version using the following commands:
USE table
COPY TO newTable TYPE FOX2X
replace table with the path and name of the DBF file, and newTable with the path and name of a new file. Then use the new file for your import. There's no guarantee this works, but the old FoxPro 2.x format is more likely to be supported by third party libraries.
If this is a repeated process, you can compile these commands into an EXE file and incorporate calling the EXE into your import process.
Replace the .NET component with the Visual FoxPro ODBC driver or OLEDB provider. The ODBC driver does not support features introduced after VFP 6, but should work in most cases. Both are only available as 32-bit drivers which might require you to use 32-bit tools to connect to the DBF file.
It might actually be a problem with one ore more records where the pointer to the memo field is wrong. You can find this with Visual FoxPro. Open the DBF file in Visual FoxPro and then open a Browse window. You can do this interactively in the menu or by executing USE and BROWSE commands.
Then double click the column saying "memo" or "Memo". If there are multiple columns, you need to repeat the following step for every column. Now click on the BROWSE window's title bar and hold down the down arrow key. Visual FoxPro should begin scrolling through the table and displaying every record. If there is an error in the memo field, you will get an error message.
Alternatively you can write a FoxPro program that uses a SCAN...ENDSCAN loop and accesses every memo field with =memofieldname if there are too many rows in the table to do this interactively.
Data Source missing
Data Source,tried to save
The issue is when I hit save to connect to a shared data source it doesn't save. When I run the report and get the below error. Then go back and the shared data source is gone. I can see that the link and extensions are null. Please help :-)
The report server cannot process the report or shared dataset. The shared data source 'SSAS_PRN' for the report server is not valid.
Problem = There was many different versions of the same data sets.
The solution was to wipe out all of them, then start fresh.
Then in Report builder.
Under the data Sources Properties.
Browse to the new version.
Hit save.
The report now works on the server.
MS Access 2010 on Windows 7 Pro x64
Right-click on a cell in a table (Data Type = OLE Object)
Click on Insert Object...
Select Create from File
Click Browse to find .bmp file (844KB)
Click OK
Receive the following error:
The operation on the OLE object failed. The OLE server may not be registered. To register the OLE server, reinstall it.
Does anyone know how to fix this issue? I've tried running Access in compatibility mode and making the database a trusted source. I am not running Norton Antivirus, which some posts say might be the problem.
#Andre and #Raju have already answered briefly in the comments, but I'm posting a proper answer for the sake of tidyness:
OLE Objects are a bit tricky, but chances are you are missing the OLE Automation Server for the file type, which in this case is - a photo editor (like Paint or Microsoft Photo Editor).
Generally I found 2 solutions you might try:
If you're coming from an older version (which is unlikely nowadays, but still), according to this Microsoft Photo Editor is removed when you install Office 2010.
If that's the case, see https://support.microsoft.com/en-us/kb/817095 on how to reinstall Microsoft Photo Editor,
Otherwise, try to restore Paint as the default application used by Access. See here https://support.microsoft.com/en-us/kb/177587 how. (Basically just remove and reinstall Paint. Instructions in the link are for an older Windows version, but I guess most steps are similar).
EDIT: note #Andre comment:
In newer Windows versions, setting File associations is not in
Explorer options, but in Control Panel Home -> Default Programs.
If you don't mind losing the existing data in your image column (or table is still empty), you can switch from the OLE Object data type to the (newer) Attachment data type.
You also gain the added value of being able to attach multiple images.
You can read more on Attachment data type here - https://support.office.com/en-us/article/Attach-files-and-graphics-to-the-records-in-your-database-d40a09ad-a753-4a14-9161-7f15baad6dbd#bm1
Good luck :)
We are using Microsoft reporting services in order to generate reports for our customers.
Today we are using the "overwrite" option when writing reports to a file share, one of our customers has now asked if would be possible to keep the last 7 copies of the rendered PDF, instead of replacing the old one each time a new report is generated.
I have looked inside the site settings for subscriptions, and can only find how to limit the number of snapshots, can this setting be used in the described scenario?
My question is: Is this possible to do with settings inside Reporting Services or do we need to use the "increment file names as newer versions are added" and then write some script that removes the old files?
Thanks!
You do not want to use snapshots, as this will require the users to go onto SSRS reporting site. If you want to keep the PDF's on a file share you would do exactly as you suggested:
The the Windows File Share subscription settings select the Increment file names as newer versions are added option.
Run a separate script to select all the files, sort them by date, and remove all but the first 7.
Can someone guide me on how can I compare schemas in SQL Server 2008.
I want to do so to check if sql objects already exists and if they exists is there any change between the existing and the new one.
You can compare schemas in SQL Server 2008 and any new SQL Server with ApexSQL Diff and it has free Community edition.
It has user friendly UI, where you can easily pick your databases (or other data sources as backups, source control projects, script folders) compare them, get results with differences and to synchronize from source to destination database.
If you just want to compare objects to only see differences and create a merge script, you can check out a free tool - ApexSQL Compare.
One more tool that can do a job that you want is dbForge Schema Compare
Get a tool such as Red Gate's SQL Compare.
You'll need to pay for it, but it pays for itself through time saved.
It is available on a trial basis if you have an immediate need.
I don't recommend you do that if you can avoid it.
If you just want to compare two SQL Server databases, I recommend a low cost alternative http://cdttools.com/sql-diff-erence/. (caveat: I wrote it).
However for what you are referring to I recommend a different approach. you should already know the different version of the various schemas for your product that you have already shipped. So build a change script based on upgrading each of them completely to your latest version. That way you installer only has to detect a single version number and chooses its sql actions based on that.
If you really really really want to do SQL comparisons during an installer yoo might want to take a look at the SMO (Shared Management Objects) that are part of the SQL server feature pack. But you will most likely have to install those before you can use them.
Then you can use them to generate the scripts for each SQl object and do a comparison in your installer. However I honestly don't recommend this.
It will tell you if they exist, and allow you to generate either "alter" or "create" script versions. Alternatively you can go directly to the INFORMATION_SCHEMA database system objects that will allow you to query directly for objects existence.
In Visual Studio 2012, go to SQL (menu item) -> Schema Compare. Click on Select Source on the left, and select the dev database. Select the production database on the right.
Then click on the generate script icon (next to the Update icon, it looks more or less like a music icon). That will generate the update script. You may also untick any of the changes that you do not want to include in the script. And it is ... 'free' if you happen to own Visual Studio 2012