Recent content by keain

Did you run delbtdll.exe in the Macola root directory to remove the 6.15 components?

I have a further question or two... so it only works on PCs that have been imaged from a source PC, correct? Has that source PC been used in production, and can it run ERS successfully?

I'm not that familiar with ERS, but you should be able to use the Pervasive ODBC without issue because Pervasive is btrieve (after btrieve 6.15, it was acquired by Pervasive who released Pervasive SQL 7). There is a btrieve 6.15 utility to control parameters such as that, but for the life of...

Good point. Save yourself some time.

If you're running Pervasive SQL 2000, the file: App: M:\Macola70\W32MKDE.EXE should not be there. There should be no btrieve components in the Macola root directory. When there is no one in Macola, and the Users directory is empty, run renbtdll.exe, which is found in the Macola root directory...

They may not have one in their profiles. You may need to copy it (and the Windows dir) to each profile. After that, get rid of the macola7.ini in c:\windows. Don't get rid of C:\windows, however... ;-)

It could be that all users in the TS environment are pulling the info from the Macola7.ini in the c:\windows dir instead of the windows dir under their profile. To test this, change the starting-progression line in the macola7.ini in the c:\windows dir to something you'll recognize (i.e. test...

Download filemon from http://www.microsoft.com/technet/sysinternals/FileAndDisk/Filemon.mspx and run it on a working workstation while the report runs. Then, run it on a non-working workstation while the report falters. Compare the two reports to find the point of failure.

Check Anti-Virus settings between the workstations, looking for variances. Also, check your Windows firewall settings.

Looks like an invalid character... Invalid character value for cast specification

Dell, however, will not put Vista on their low end Dimensions, which is what I imagine Randva uses. On the optiplexes, which are the business class machines, you can have XP loaded without a fight. Dell will also sell you an enterprise or volume license for XP, so you can get the machines with...

If what Andy says is the case and you're on XP, roll back XP to a date in time prior to the problem occurring and see if it recurs. If it does, apply the XP patches one by one until you find the one that breaks the system, roll it back and then decline it.

I wouldn't hold out much hope, just because of the tightened security. That being said, Vista allows you to run applications in what amounts to an emulation mode of older operating systems (95, 98, 2000, XP, etc.). Perhaps that would be the way to go. However, if the budget permits, bring on...

Off the top of my head, either a dll/ocx is the wrong version or unregistered. In the Macola Shared, Windows\System, Windows\Ssytem32 and the flex folder, run the following command for %1 in (*.dll, *.ocx) do regsvr32 /s %1

I haven't seen it on 7.6.400, mainly because I haven't seen Progression since 7.6.300...but I've seen the issue happen during upgrades. It had multiple causes, and I'll present the two I've experienced. 1. Update scripts hose syspass and/or syscomp tables. With one client, they restored back...