Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 18 MAR 2004 02:02:14PM Clark Westfield wrote:

I have a client who I am trying to attach their AREV tables in OpenInsight 4.1.3. Both AREV and OI are using the All Networks 2.1 driver. The AREV tables cannot be accessed via the Database Manager (using FILE ADD menu) or the System Monitor (using ATTACH_TABLE command). The Database Manager shows no tables, the System Monitor returns 'FS109 Invalid Volume Name' error. The Service is not running and the REVPARAM files have been renamed to REVPARAM1.

The AREV application is in p:\arev

The AREV data is in p:\arev\data

The OI application is in p:\revsoft\oinsight

I copy the AREV data to p:\revsoft\oinsight\data and the Database Manager works fine.

Full permission is given to each of the arev and revsoft directories.

Any ideas as to why the Database Manager would not show the tables?

Thank you,

Clark Westfield


At 22 MAR 2004 12:36PM Warren wrote:

Maybe the DBT file is corrupted. Backup the account.dbt file and try copying the SYSPROG.DBT file over it and starting over.


At 22 MAR 2004 02:16PM Clark Westfield wrote:

Thanks for the reply. I replaced the dbt file and there was no difference.

Clark


At 22 MAR 2004 03:32PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

Clark,

What happens if you run 'RUN LIST_VOLUME "p:\arev\data"' from the Exec line in the system monitor? Still the same error? (This version of the database manager won't show anything if it finds an error - nor will it report it back :(, using the command line utilities in System Editor is the best options here)

What happens if you copy the data to another drive or another location apart from OI (which you've already tested). Can you attach it using a UNC name instead of a mapped drive?

The Sprezzatura Group

World leaders in all things RevSoft


At 22 MAR 2004 04:07PM Clark Westfield wrote:

List_Volume returns an FS109 Invalid Directory error. I have not tried UNC. If I map to a different drive letter I receive the same errors.

Clark

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/4a8f76b10ec896cb85256e5b00631519.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1