dbexp utility with db_Vista version 3.0

[mary.davis.1986]

Am trying to export using dbexp utility.

When I run the import I get the following error.
<<<<<<<<<<<<<<<<<<<<<<<<<<
C:\Database>dbexp InvData

dbexport - Database Export Utility
RDM Embedded 10.0.0 Build 741 [7-15-2010] http://www.raima.com/
Copyright (c) 2010 Raima Inc., All rights reserved.

PROGRAMMER/USER error: -4
can not open dictionary
C errno = 0: No error
FILE: d:\buildagent\workspace\root\rdme\10.0\build\rc\source\runtime_nu\../runti
me/inittab.c(1033) (errnum = -4)

ERROR 69
RDMe Status: -4 (can not open dictionary)
dbexp_util.c (645)

PROGRAMMER/USER error: -1
database not opened
C errno = 0: No error
FILE: d:\buildagent\workspace\root\rdme\10.0\build\rc\source\runtime_nu\../runti
me/enter.c(59) (errnum = -1)
>>>>>>>>>>>>>>>>>>>>>>>>

I've tried different dbexp parameters by I always get the data dictionary error.

I copied the dbexp utility into my database folder to run this.

Is there a problem with the syntax I'm using. This is for a one time export.

Thank you

[dwilson]

Hi Mary,

RDM Embedded 10.0 works a little differently from previous versions, as it is now a client-server database, as I'm sure you've noticed! The problem is that the Transactional File Server (TFS) can't find the database. It's expecting the DBD and all the database files to be in a subdirectory of its document root directory. For example, if you install a 32-bit Windows version of RDM Embedded 10.0 in C:\rdme10 then the document root would normally be C:\rdme10\databases.win32. The document root can be any directory, as specified with the -d option when you start the TFS (tfserver.exe). However, at installation time a directory called databases.win32 is created for the example databases supplied with the product.

So, if your database is called InvData, you will need to create a subdirectory called InvData under the TFS document root, (e.g. C:\rdme10\databases.win32\InvData) and copy all the database files into it, including the DBD file. Now you should be able to run dbexp - it doesn't matter where dbexp.exe is located, as long as it's on the system path.

Regards,
Douglas Wilson

[mary.davis.1986]

Douglas,

Thanks you for the information.

The export is working for me now.

Mary