EMS sq. manager 2008 for interbase for firebird not importing XML properly.

Asked By 50 points N/A Posted on -
qa-featured

Ems sq. manager 2008 for inter base for firebird latest version is supposed to import XML formats but mine does not. Is anybody else facing the same problem?

SHARE
Answered By 0 points N/A #147210

EMS sq. manager 2008 for interbase for firebird not importing XML properly.

qa-featured

Hi,

Try the following steps:

  1. Check the system files for any errors. If there are any errors then try to fix them using the system files tool.
  2. In order to import xml formats your system should be compatible with the latest version of firebird. If there is a compatibility error then you have to use the version that is supported by your computer.
  3. Check the bin files on your computer for any errors. If there are any errors then you can repair them using the scf/scannow command in the command prompt window. This command automatically repairs all the corrupted bin files.

Hope this information helps you.

 

Answered By 565040 points N/A #147211

EMS sq. manager 2008 for interbase for firebird not importing XML properly.

qa-featured

If you are using EMS SQL Manager for InterBase/Firebird 2008, check the Firebird server version that you are using because it may no longer be compatible with your current SQL Manager. Try using EMS SQL Manager for InterBase/Firebird 5.2. As of the moment, this is their latest version. Visit EMS SQL Manager for InterBase/Firebird to download. In this version, Microsoft Windows 7, Windows 8, and Windows 8.1 are now supported.

They also added preliminary support for InterBase 2009 as well as support for EUA or Embedded User Authentication for InterBase 7.5 and higher. It supports activating/deactivating, editing, duplicating, creating, and deleting of new object. If you are using Firebird 2.5, you can now create a view from stored procedure. The issue with InterBase Desktop Edition servers where you cannot establish a connection to a database using the Local protocol was already fixed.

The issue with NTLM authentication where connecting to a host causes an error was already fixed.

Login/Register to Answer

Related Questions