Linking GoldMine Tables to MSACCESS

[Guest]

One of the Goldmine tables linked using the dbase V driver is showing about
2000 records short on some TMS sessions. Other sessions are OK. My queries on
the bad sessions are not working. Is there a fix?

 

[Immanuel Sibero]

Hi,

You're throwing in Goldmine terminologies with which many people in this
newsgroup are not familiar. They are very knowledgeable about MS-Access but
not necessarily Goldmine.

In my office, we use Goldmine and I have applications in Access that link to
the goldmine tables but I have no clue what TMS sessions are. When queries
are "not working", what really happens? Do the queries choke? Do they throw
up an error message?

Could you elaborate?


Immanuel Sibero

 

[Rob Diamant]

Try cleaning up your goldmine database. the records access is choking on are
probably "deleted" records that have not been physically removed. when you
try and filter against these records access will fail.

Rob

 

[Immanuel Sibero]

Frank,

If you're not aware already, I forgot to mention that Goldmine has pretty
lively newsgroup as well:

gmnews.goldminesw.com

There is a number of Goldmine experts who hang out there that I'm sure can
resolve your issue.

HTH,
Immanuel Sibero

 

[Guest]

Thank you for responding,
TMS is Terminal Services which means all 25 users are sharing the exact same
MSACCESS database in separate sessions on a Windows 2000 Server Service Pack
4. Contact1.dbf is one of the Goldmine tables linked to the database. All
Users are looking at the exact same table; but some see 25000 records some
see 23000. If I sort the table, all 25000 records appear. Queries run fine on
the good session. On the bad sessions, I see the word "#deleted" in a number
of fields.

Hi,

You're throwing in Goldmine terminologies with which many people in this
newsgroup are not familiar. They are very knowledgeable about MS-Access but
not necessarily Goldmine.

In my office, we use Goldmine and I have applications in Access that link to
the goldmine tables but I have no clue what TMS sessions are. When queries
are "not working", what really happens? Do the queries choke? Do they throw
up an error message?

Could you elaborate?


Immanuel Sibero

 

[Guest]

Rob,
We rebuild the indexes every night. The weird behavior is, everyone is
theoretically, Linked to the exact same Goldmine table, but different
sessions get different record counts. My interim solution is to limit queries

Try cleaning up your goldmine database. the records access is choking on are
probably "deleted" records that have not been physically removed. when you
try and filter against these records access will fail.

Rob

 

[Rob Diamant]

By cleanup, I mean not only rebuilding the indexes but also removing the
#Deleted records by compacting the database.

Rob,
We rebuild the indexes every night. The weird behavior is, everyone is
theoretically, Linked to the exact same Goldmine table, but different
sessions get different record counts. My interim solution is to limit
queries

 

[Immanuel Sibero]

Hi Frank,

It is interesting that you're getting different results, given that you're
using the same MSAccess.
What version of access?
Do you have the latest service pack? and latest Jet update?

I vaguely remember having similar issues with "#deleted" using Access 2000
connecting to IBM DB2. Service Packs took care of the problem

Immanuel Sibero

Thank you for responding,
TMS is Terminal Services which means all 25 users are sharing the exact same
MSACCESS database in separate sessions on a Windows 2000 Server Service Pack
4. Contact1.dbf is one of the Goldmine tables linked to the database. All
Users are looking at the exact same table; but some see 25000 records some
see 23000. If I sort the table, all 25000 records appear. Queries run fine on
the good session. On the bad sessions, I see the word "#deleted" in a number
of fields.