How to Store Datalogs in FactoryTalkView SE and Resolve DBF File Issues

The ODBC dBASE drivers are believed to originate from Office, particularly the "Jet Engine" on which MS Access is built. The Jet Engine used to be freely available for separate installation, and it still appears to be so. You can download the Microsoft Access Database Engine 2016 Redistributable from the Official Microsoft Download Center. To check if the dBASE driver is installed, use the ODBC Administration Tool. Remember that a .DBF "database" is essentially a directory, with the tables being files within it.

• 01-09-2024
• Cheeseface

The instructions provided were adequate, but there were a few details missing. I followed the steps on a single computer, avoiding the need to transfer files between machines. One key action I took was creating a dedicated "database" folder to keep all files organized in one place, which proved essential for step #7 when saving DBF files in a specific location for easy access. Additionally, my version of Access no longer automatically generates .MDB files, so I had to utilize the "Save As" function and select the MDB format, opting for the 2002 version. In step #10, it is crucial to click the browse button next to each table to choose the DBF versions. Once I sorted out these details, I successfully logged into the DBF database.

• 02-09-2024
• Operaghost

I recently faced the same issue when transitioning from RSView32 to FactoryTalk View SE. The problem lies in the different formats of datalogs in RSView32 (*.DBF) and FactoryTalk View SE (*.DAT). As you pointed out, FT View SE doesn't support *.DBF files, so the traditional approach to generating Excel reports won't work. What worked for me was using a third-party tool like Kepware's DataLogger, which reads the *.DAT file from the FT View SE and converts the data into a format that can be easily assimilated into Excel. It might take a bit to set up, but once done, it's a fairly smooth process. I'd highly recommend starting with their trial version to see if it meets your needs before making any investment.

• 10-01-2025
• Logan Flores

I’ve faced a similar transition when upgrading to FactoryTalkView SE, and it can be quite the hassle with the datalog format change. One thing that helped me was using a third-party tool to convert the *.DAT files back into a more familiar format, which made it easier to integrate with Excel for reporting. Another approach I found useful was reaching out to Rockwell's support team directly; they were really responsive and walked me through a few specific steps that weren't covered in the KnowledgeBase article you mentioned. If you haven't tried that yet, it might be worth a shot!

• 01-03-2025
• Madison Adams

I've been through a similar transition recently, and I found that using the built-in data export options in FactoryTalkView SE really helped bridge the gap. Have you tried exporting the DAT files to a format that Excel can read, like CSV? It might require some extra steps, but it could save you the hassle of dealing directly with the DAT format. Also, I'd recommend reaching out to Rockwell support if you're still stuck; they can offer specific advice tailored to your setup. Hope that helps!

• 01-03-2025
• Jacob Moore