Catobase Issue

TotalEnd98 · 10-04-2004, 12:51 PM

Catobase 6.1.4 ran fine for me for quite a while. But the other day, I started having this problem. If I create a new database, I get three error messages, in order:

Method '~' of object '~' failed
Database connection failed
Invalid procedure call or argument

Opening any database gets me the first and third error message.

I found the 6.1.4 .zip and replaced my versions of the .exe and default .mdb with ones fresh from the zip. That had no effect.

Any help is appreciated.

TotalEnd98 · 10-13-2004, 04:11 PM

Bump... uninstalling and reinstalling didn't help, either.

Anyone have any ideas?

jbmagic · 10-13-2004, 04:17 PM

you install the exporter too?

DaveHorn · 10-13-2004, 05:34 PM

Have you installed Win XP SP 2 in between when it worked and it didn't. I wonder if XP SP 2 has a conflict with Cato???

Deitrus · 10-13-2004, 08:47 PM

Quote:

Originally Posted by DaveHorn

Have you installed Win XP SP 2 in between when it worked and it didn't. I wonder if XP SP 2 has a conflict with Cato???

Most likely since SP-2 has problems with almost everything else.

I've since uninstalled SP-2 until MS clears up the bugs.

Ktulu · 10-13-2004, 10:56 PM

Quote:

Catobase 6.1.4 ran fine for me for quite a while. But the other day, I started having this problem. If I create a new database, I get three error messages, in order:

Just a guess, but sometimes Catobase has problems with long directory names

TotalEnd98 · 10-14-2004, 12:44 AM

Quote:

Originally Posted by jbmagic

you install the exporter too?

Yes. Like I said, it worked fine for quite a while, then didn't. It won't even load a database, so the exporters never come into play.

TotalEnd98 · 10-14-2004, 12:45 AM

Quote:

Originally Posted by DaveHorn

Have you installed Win XP SP 2 in between when it worked and it didn't. I wonder if XP SP 2 has a conflict with Cato???

No. I did, however, reinstall Windows XP SP 1, in an attempt to clear up another issue I've been having (it didn't work). Catobase has never had a problem with Windows reinstallations before, though, and no other program has given me an issue.

TotalEnd98 · 10-14-2004, 12:46 AM

Quote:

Originally Posted by Ktulu

Just a guess, but sometimes Catobase has problems with long directory names

Unfortunately, the answer's probably not that simple. F:\Catobase wasn't long back in the DOS 5.1 days. =)

DaveHorn · 10-14-2004, 12:20 PM

Catobase uses some specific M$ DLLs. DAO objects or some such nonsense. I think when you install 5.40 the first time it mentions them and the specific requirements. If you had to reinstall XP SP 1, maybe you no longer have those components?

Do you have Access? If so, can you open the mdb in Access by itself?

It seems like some sort of OS issue and not a CATO.

TotalEnd98 · 10-14-2004, 01:50 PM

Quote:

Originally Posted by DaveHorn

Catobase uses some specific M$ DLLs. DAO objects or some such nonsense. I think when you install 5.40 the first time it mentions them and the specific requirements. If you had to reinstall XP SP 1, maybe you no longer have those components?

Do you have Access? If so, can you open the mdb in Access by itself?

It seems like some sort of OS issue and not a CATO.

Opens fine in Access 2003. As for the other components, they were installed when I reinstalled 5.4.0 yesterday. No help there.

DaveHorn · 10-14-2004, 02:31 PM

Quote:

Originally Posted by TotalEnd98

Opens fine in Access 2003. As for the other components, they were installed when I reinstalled 5.4.0 yesterday. No help there.

Hmmm, I'm totally out of ideas on new things to try. I'll keep my eye on the thread in case I think of anything else.

TotalEnd98 · 10-15-2004, 02:35 PM

Problem solved. While MDAC 2.6 is required and always worked for me before, apparently CatoBase grew sentient and demanded MDAC 2.8 to continue working, a ransom I gladly paid.

10-04-2004, 12:51 PM	#1
TotalEnd98 All Star Starter Join Date: Dec 2001 Location: New York Posts: 1,687	Catobase Issue Catobase 6.1.4 ran fine for me for quite a while. But the other day, I started having this problem. If I create a new database, I get three error messages, in order: Method '~' of object '~' failed Database connection failed Invalid procedure call or argument Opening any database gets me the first and third error message. I found the 6.1.4 .zip and replaced my versions of the .exe and default .mdb with ones fresh from the zip. That had no effect. Any help is appreciated. __________________ OTBL - Scandinavia Cartoon Heroes This is the way the world ends Not with a bang but a whimper.

10-13-2004, 04:11 PM	#2
TotalEnd98 All Star Starter Join Date: Dec 2001 Location: New York Posts: 1,687	Bump... uninstalling and reinstalling didn't help, either. Anyone have any ideas? __________________ OTBL - Scandinavia Cartoon Heroes This is the way the world ends Not with a bang but a whimper.

10-13-2004, 05:34 PM	#4
DaveHorn All Star Starter Join Date: Aug 2003 Posts: 1,146	Have you installed Win XP SP 2 in between when it worked and it didn't. I wonder if XP SP 2 has a conflict with Cato??? __________________ Dave HFTC Commish

10-14-2004, 12:20 PM	#10
DaveHorn All Star Starter Join Date: Aug 2003 Posts: 1,146	Catobase uses some specific M$ DLLs. DAO objects or some such nonsense. I think when you install 5.40 the first time it mentions them and the specific requirements. If you had to reinstall XP SP 1, maybe you no longer have those components? Do you have Access? If so, can you open the mdb in Access by itself? It seems like some sort of OS issue and not a CATO. __________________ Dave HFTC Commish

10-15-2004, 02:35 PM	#13
TotalEnd98 All Star Starter Join Date: Dec 2001 Location: New York Posts: 1,687	Problem solved. While MDAC 2.6 is required and always worked for me before, apparently CatoBase grew sentient and demanded MDAC 2.8 to continue working, a ransom I gladly paid. __________________ OTBL - Scandinavia Cartoon Heroes This is the way the world ends Not with a bang but a whimper.

10-13-2004, 04:17 PM	#3
jbmagic Hall Of Famer Join Date: Sep 2003 Location: Los Angeles Posts: 3,417	you install the exporter too?