ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Installation >> Btrieve Error 11
http://www.istechforum.com/YaBB.pl?num=1210917312

Message started by runner1717 on 05/15/08 at 22:55:12

Title: Btrieve Error 11
Post by runner1717 on 05/15/08 at 22:55:12

Have a workstation that returns a Btrieve error 11 when attempting to start DBA. The client loads fine on the server(win 03). No other workstations to test from.

I'm pretty dumb when it comes to DBA and Pervasive so speak s l o w..... ;-)

What causes the error 11?

Thanks for the help!

Mike

Title: Re: Btrieve Error 11
Post by kkmfg on 05/16/08 at 04:28:34

Error 11 means "The specified filename is invalid." Is there a filename listed when that error comes up?

You can look the error up yourself by going to Start -> Programs -> Pervasive -> Documentation -> Pervasive.SQL 9 (Or whatever version you have). Once that loads click the index tab and scroll down until you find 11. Click on that and read it.

My guess is that you've got spaces in your filename somewhere and dba doesn't like it.

PS: From your description I gather you are using the client/server version of Pervasive? Or are you using workgroup?

Title: Re: Btrieve Error 11
Post by runner1717 on 05/16/08 at 08:41:34

You are correct. It's a client / server installation.

I don't have to deal with the DBA installation very often. In a client / server installation is there a client install of DBA and/or Pervasive to the client or do I just make a shortcut to the DBA executable on the server?

The installation was working fine. Now it's not. Could the error 11 be drive LETTER oriented?

Thanks,

Mike

Title: Re: Btrieve Error 11
Post by kkmfg on 05/16/08 at 09:17:44

runner1717 wrote:

You need the client version of PervasiveSQL on the client. Then you map a drive letter (doesn't matter what it is) and create a link directly to the DBA executable. At least, you can do that in DBA Classic. In Evo you run the evoerpsetup program from the server and it sets up a local C:\ISTS folder on the client.

I am unaware of any problem if the drive letter to DBA changes. At least, so long as it does not change while the program is running. Especially if you use C/S because then all data files just stay on the server and the drive mapping doesn't matter.

Title: Re: Btrieve Error 11
Post by Lynn_Pantic on 05/16/08 at 17:36:44

I have seen issues if drive mapping is changed, the desktop icon gets confused. Get rid of the icon and (for DBA Classic) simply browse to the DBAMFG folder on the server and double click on TP5WDBA.EXE. If it loads, then create a new icon pointing to that executable.