Welcome, Guest. Please Login.
03/28/24 at 02:51:03
News:
Home Help Search Login


Pages: 1
Send Topic Print
Btrieve Error 35 (Read 15404 times)
gaburto
Browser
*


I Love EvoERP!

Posts: 3
Btrieve Error 35
05/12/09 at 19:37:15
 
I am running EVOERP  build 12/22/08
 
I am getting error [Pervasive][ODBC Client Interface][LNA][Pervasive][ODBC Engine Interface][Data Record Manager] The Btrieve file directory is invalid (Btrieve Error 35)
 
Is there a step by step procedure to setup the ODBC connection? We are running Small Business Server 2003.
 
Thanks
George
Back to top
 
 
Email   IP Logged
gaburto
Browser
*


I Love EvoERP!

Posts: 3
Re: Btrieve Error 35
Reply #1 - 05/12/09 at 19:58:45
 
Ok I can now connect, but now in MSAccess I see no tables?
 
Again is there a step by step guide to connect using ODBC.
 
I have a setup other ODBC connections before.
Back to top
 
 
Email   IP Logged
Lynn_Pantic
Administrator
*****


evolution (n) -
gradual change to a
different form

Posts: 5681
Re: Btrieve Error 35
Reply #2 - 05/12/09 at 20:28:17
 
In DBA/Evo, run UT-A, ODBCDDF to create the DDF files
Back to top
 
 

Lynn Pantic
IS Tech Support
lynn@istechsupport.com
Email   IP Logged
gaburto
Browser
*


I Love EvoERP!

Posts: 3
Re: Btrieve Error 35
Reply #3 - 05/12/09 at 20:49:44
 
Ok,
 
I am now getting the error 35 again.  My ".B" are in the default\ directory.  Is this where they are suppose to be?  Is there any way I can get a step by step instructions on how to setup the ODBC connection.
 
thanks
George
Back to top
 
 
Email   IP Logged
Lori
Browser
*




Posts: 40
Gender: female
Re: Btrieve Error 35
Reply #4 - 08/28/09 at 12:01:43
 
I'm having a similar problem?  Years ago we bought CR v.10 but it wasn't compatible with DBA so our DBA consult shared his 9 version with us.  Recently our IT guy deleted CR when he was installing a new harddrive in my computer; so he found a 9.22 version for us to use.  
 
Our old reports are opening up in it, but its not connecting to the data.  We get the message:
Not supported.
Details: Btrieve [35] : Directory error.
 
Dennis W tried a bunch of fixes but we keep getting the same message.  Can anyone help us out?
 
Thanks
Back to top
 
 

DBA Classic since 1997, some users on EVO since 8/09
Current Version
Windows NT Server 2000
10 workstations
  IP Logged
kkmfg
Senior Member
****


Ghost of the code

Posts: 411
Gender: male
Re: Btrieve Error 35
Reply #5 - 08/31/09 at 04:26:28
 
Well... As you might guess, that error means that btrieve cannot access the directory with the data files. This could be for a number of reasons:
 
1. Maybe you don't have the drive mapped or connected? Can you use windows explorer to go to where the files are located and see them?
2. Maybe something is wrong with your DDF files? Have you tried rerunning ODBCDDF?
   2a. It's possible that your DDF files are pointing to a directory which doesn't actually exist. Maybe you changed drive letters or something?
3. Maybe there is a server or workstation problem? Can you successfully run evo/dba from the machine in question?
Back to top
 
 

Collin
K & K Manufacturing, Inc

EvoERP Version 1-22-10 SP3
5 User Workgroup Pervasive 10
Email WWW   IP Logged
Lori
Browser
*




Posts: 40
Gender: female
Re: Btrieve Error 35
Reply #6 - 08/31/09 at 13:34:13
 
I know nuttin' about driving or mapping...  cry
 
I ran UT-A for ODBCDDF and got this error message:
 
Working on WBTRVMEM
File Name BTRV.MEM.CNTR
 
Btrieve error:  \\wikknt\dbamfg\DEFAULT\File.DDF-5
 
When I hit OK it continued through.  However, my CR still gets error 35.
 
My e-mail techsupport suggested I post here cuz he doesn't know what to do either...  Grin
Back to top
 
 

DBA Classic since 1997, some users on EVO since 8/09
Current Version
Windows NT Server 2000
10 workstations
  IP Logged
Lynn_Pantic
Administrator
*****


evolution (n) -
gradual change to a
different form

Posts: 5681
Re: Btrieve Error 35
Reply #7 - 08/31/09 at 20:52:33
 
Error 5 is a Duplicate Key - you can typically click OK and generate the DDFs and operate with no problem.
 
Error 35 is a Directory error - that is different and relates to drive maps and permissions.
Back to top
 
 

Lynn Pantic
IS Tech Support
lynn@istechsupport.com
Email   IP Logged
cathyh
Active Member
*****


I used to be
indecisive; now I'm
not so sure......

Posts: 1213
Gender: female
Re: Btrieve Error 35
Reply #8 - 09/01/09 at 07:21:35
 
Is your DBA folder shared?  I recently updated and had changed the folder to not shared but with read and write permissions for all my users; when the workstations tried to log in to Evo the message was that Pervasive could not find the ddf's.  After I shared the folder on the server, workstations could log in.  I am running Pervasive 10.
Back to top
 
 

Cathy Hamilton
Wing Inflatables, Inc.
EVO-ERP2008.1(20 users) w/IS Tech update 5/25/09 (as of 08/21/09)
Windows 2008 Server/client
Pervasive V10.1
Email WWW   IP Logged
dameng
Senior Member
****


DBA / EVO Software
Consultant

Posts: 275
Gender: male
Re: Btrieve Error 35
Reply #9 - 09/18/09 at 11:21:56
 
your version of Crystal Report has nothing to do with either btrieve error. every report keeps it's information of how it was connecting to the database when it was first designed. if that connection doesn't exist, or has changed, then hence the btrieve 35 error.
how to fix, depends on the connection your report is using. and as such, if more than one person runs the same report, then they have to have identical path that the report was using.
 
if you want, i can remote your computer and we can fix your btrieve error situation with your Crystal Reports.
email me, or call, davemeng@earthlink.net or 760-832-2536  
Back to top
 
 

Dave Mengelkamp
Digital Consulting
760.832.2536
davemeng@earthlink.net
Email WWW   IP Logged
Pages: 1
Send Topic Print