jrri
asked on
table names show up different on certain computers using Pervasive database
we use a program that uses pervasive as the database. we've created an access database that connects via an odbc. one group of computers sees the table name one way and the other group sees it another. we can't pinpoint what is the difference. the odbc looks the same on both groups.
obviously the database doesn't work on one group because they see the table names different.
I suppose the question is: what could make them see the table names differently?
obviously the database doesn't work on one group because they see the table names different.
I suppose the question is: what could make them see the table names differently?
ASKER
I've tried a network based access DB and a local result is the same
not using PCC, pervasive DB is from an estimating program called Timberline
name difference: fred_bob_joe on one and when you try to link from the other computer it sees it as bob__fred_joe. it's weird, it moves which word is in front and on one position it adds another underscore.
not sure what a DDF is.
not using PCC, pervasive DB is from an estimating program called Timberline
name difference: fred_bob_joe on one and when you try to link from the other computer it sees it as bob__fred_joe. it's weird, it moves which word is in front and on one position it adds another underscore.
not sure what a DDF is.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i'll try to check on some of your suggestions
, the quick fast fix is to simply rename the linked tables to match what the other groups looks like and it works but obviously there is a bigger issue.
, the quick fast fix is to simply rename the linked tables to match what the other groups looks like and it works but obviously there is a bigger issue.
If you use PCC (Pervasive Control Center), are the table names different or the same?
What exactly is different about the names?
The only time I've seen this type of behavior is when the PSQL Database Name is pointing to a different set of DDFs and the sets are not the same.