Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
6.15 TCP/IP
- Thread starter merhottin
- Start date
We went up to version 7.0 before attempting TCP/IP...
That aside could it be the users permission? In one of our manuals 94 is described as:
A user attempted to open or create a file in a directory where they have those rights. BTRIEVE does not override the network privileges assigned to users.
What if you were looged in as the system administrator - does that make any difference?
Is it a DOS or a Windows application? We found that DOS isn't as strict with permissions as Windows when it comes to accessing btrieve.
That aside could it be the users permission? In one of our manuals 94 is described as:
A user attempted to open or create a file in a directory where they have those rights. BTRIEVE does not override the network privileges assigned to users.
What if you were looged in as the system administrator - does that make any difference?
Is it a DOS or a Windows application? We found that DOS isn't as strict with permissions as Windows when it comes to accessing btrieve.
- Thread starter
- #3
Tom, thanks for the info.
We have tried supervisor, same problem.
It is a windows application.
Funny part is, the application can run on our windows 2000 server, but not any of the windows 98 work stations.
The server is a novel netware server. I strongly beleive it has something to do with the TCP change we made. We are going to back that change out this afternoon, and see if that works.
Thanks for the information again.
We have tried supervisor, same problem.
It is a windows application.
Funny part is, the application can run on our windows 2000 server, but not any of the windows 98 work stations.
The server is a novel netware server. I strongly beleive it has something to do with the TCP change we made. We are going to back that change out this afternoon, and see if that works.
Thanks for the information again.
We are in the process of upgrading to P.SQL8. We were getting 94 errors - it turned out that it wasn't permissions but merely configuration on the server side. We switched off the multihomed session we ensured that both local and remote access was switched on. We set the file version to 7.x instead of 8.x - and a bit of tweaking and it seemed to work.
Best of luck,
Tom
Best of luck,
Tom
MacolaHelp
Instructor
wrq32cfg.exe was the utility you had to run on 6.15 to configure the client machines to run either spx or tcp, which sets values in the bti.ini as well as the registry.
In version 7, you have to set the tcp in the client 16 & client 32 programs on the pervasive group, which in turn sets registry entries. I often had to manually edit the registry, though.
I don't think I'd try to run a winnt or xp client on either 6.15 or 7. They haven't been supported by pervasive for years.
In version 7, you have to set the tcp in the client 16 & client 32 programs on the pervasive group, which in turn sets registry entries. I often had to manually edit the registry, though.
I don't think I'd try to run a winnt or xp client on either 6.15 or 7. They haven't been supported by pervasive for years.
- Status