

I looked at existing installations and installed things such as Visual C++ redistributables from various years, and that cleared up some of the errors I was getting, but I still struggled with blank reports and some reports still threw errors. I asked the vendor what dependencies his program requires, so I could make sure to provide a similar environment to that of his development setup, but he said no prereqs are needed at all. I paid to renew our company's "support," so I could obtain the newest copy, but this problem persisted. Many of these reports were created years ago based on their creation dates, but I guess that doesn't matter, since they query current records from SQL.Īll of this is well-and-good, except for one thing as I start to replace peoples' aging computers, I run into problems where DataLink on their new computer fails to live up to expectations, and either throws errors or displays blank screens instead of reports filled with fields and numbers. I know very little about this aspect of the world of tech, but best I can understand, these RPT files reference a 32 bit ODBC connection which points back to a SQL database on a server, and when the report is accessed, it displays a snapshot of what the data looks like in that moment.

One of the big pieces of frustration I'm having involves a network share FULL of RPT files that are currently being accessed by a variety of individuals using DataLink Viewer. Thankfully, there's one individual who remains at the company who has bits and pieces of understanding, but not 100% when it comes to this question. Shortly after my arrival, my boss left without imparting very much insight of the company's technical landscape. I recently joined a company working as a desktop tech & other various technical roles.
