Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Remote Users and Notes/History
1 view
Skip to first unread message
rb...@my-deja.com
Sep 28, 2000, 3:00:00 AM9/28/00
to
Anyone ever had a problem with a remote user not getting all of HIS
Notes and History? they are not being removed due to date. User sees
older notes and you can add a new activity and it will show as a
history item. But, there are about 20-30 notes and history items that
are not showing up (that we know of). I have checked every setting I
can think of, rebuilt the security cache, cut a new database and still
can't get all of his notes to him. I however can see them on a
workgroup machine so I know the entries exist in the dbase. ANy help
out there? Have called Saleslogix Tech support and not getting much
help there. Thanks. Running SLX version 3.1.6
Notes and History? they are not being removed due to date. User sees
older notes and you can add a new activity and it will show as a
history item. But, there are about 20-30 notes and history items that
are not showing up (that we know of). I have checked every setting I
can think of, rebuilt the security cache, cut a new database and still
can't get all of his notes to him. I however can see them on a
workgroup machine so I know the entries exist in the dbase. ANy help
out there? Have called Saleslogix Tech support and not getting much
help there. Thanks. Running SLX version 3.1.6
Sent via Deja.com http://www.deja.com/
Before you buy.
Kari
Sep 29, 2000, 3:00:00 AM9/29/00
to
Can _other_ remotes see those notes? If not check the userID on those
notes in the history table. I don't know how - but perhaps that info
is missing or inaccurate? OR have you removed that user and then re-
added him so that he actually has a different user ID than before? At
any rate check the user IDs on the history.
A work around may be to try resending via sync the accounts that the
notes are missing from to see if he gets all the notes that way. I
have done this to get notes to people who added history after I had
created a new database for them but before they had the new DB
installed.
notes in the history table. I don't know how - but perhaps that info
is missing or inaccurate? OR have you removed that user and then re-
added him so that he actually has a different user ID than before? At
any rate check the user IDs on the history.
A work around may be to try resending via sync the accounts that the
notes are missing from to see if he gets all the notes that way. I
have done this to get notes to people who added history after I had
created a new database for them but before they had the new DB
installed.
In article <8r0782$jk2$1...@nnrp1.deja.com>,
steve_v...@my-deja.com
Oct 3, 2000, 3:00:00 AM10/3/00
to
I found a massive bug in Saleslogix where the Notes/History of deleted
users does not get Sync'd down to remotes. This has been reported as a
defect and they are currently working on it. THe work around:
users does not get Sync'd down to remotes. This has been reported as a
defect and they are currently working on it. THe work around:
Run a SQL statement against the History table looking for all History
with Userid set to NULL. Run another statement changing this userid to
a space " ". Then re cut a database. The history will be there.
In article <8r2oio$alq$1...@nnrp1.deja.com>,
bu...@nsf.org
Oct 3, 2000, 3:00:00 AM10/3/00
to
Thanks Steve, great info, but we have fixed our problem and it was due
to an "insuficient memory for this operation" error during creation of
this users remote database. The error occurs during the creation of
the History table. Hard to notice unless you sit and watch the entire
creation because the creation continues normally and you end up with a
good database without all the notes and history. Apparently our
database has grown so much we are running into this now. Our fix was
to change the memsize, memsharesize and TDS packets in the BDE
administrator. Just kept raising them until the database cut without
error. Just thought you all should know. Thanks for the help.
to an "insuficient memory for this operation" error during creation of
this users remote database. The error occurs during the creation of
the History table. Hard to notice unless you sit and watch the entire
creation because the creation continues normally and you end up with a
good database without all the notes and history. Apparently our
database has grown so much we are running into this now. Our fix was
to change the memsize, memsharesize and TDS packets in the BDE
administrator. Just kept raising them until the database cut without
error. Just thought you all should know. Thanks for the help.
In article <8rcpoe$op5$1...@nnrp1.deja.com>,
steve_v...@my-deja.com
Oct 6, 2000, 3:00:00 AM10/6/00
to
Burr what did you change those settings too? We have the Insufficient
mem errors as well.
Also that bug I reported does still excluded Notes/History. I would
check that if you lose employees every so often.
mem errors as well.
Also that bug I reported does still excluded Notes/History. I would
check that if you lose employees every so often.
In article <8rdc97$9q8$1...@nnrp1.deja.com>,
Kari
Oct 9, 2000, 3:00:00 AM10/9/00
to
Hi-
Where exactly do you find these items in order to change them? Also if
the database creation was bombing on the history and you have stopped
that aren't you ending up with a database too large for Interbase to
handle well? How is the performance on this remote now?
Where exactly do you find these items in order to change them? Also if
the database creation was bombing on the history and you have stopped
that aren't you ending up with a database too large for Interbase to
handle well? How is the performance on this remote now?
K.
mea...@my-deja.com
Oct 10, 2000, 3:00:00 AM10/10/00
to
Just to throw another thing in the mix, if you are running MSSQL7, make
sure you have installed sp2 before making changes to the TDS packet
size.
If you increase the size of the TDS packets, you can introduce nulls
into the packet information headers and crash your SQL Server.
This is due to a bug in MSSQL7 that was fixed with sp2.
sure you have installed sp2 before making changes to the TDS packet
size.
If you increase the size of the TDS packets, you can introduce nulls
into the packet information headers and crash your SQL Server.
This is due to a bug in MSSQL7 that was fixed with sp2.
I have yet to install sp2 on a server and have problems (I have
installed it about a dozen times) so if you have not, I would recommend
it.
In article <8rt3oc$dfr$1...@nnrp1.deja.com>,
K
Oct 12, 2000, 3:00:00 AM10/12/00
to
Thanks for the warning. i was just checking out the SLX support site
though and notice that they don't list SP2 in their compatability list
though. I may drop them an email to see why not.
-K
though and notice that they don't list SP2 in their compatability list
though. I may drop them an email to see why not.
-K
In article <8rvji4$dka$1...@nnrp1.deja.com>,
steve_v...@my-deja.com
Oct 19, 2000, 3:00:00 AM10/19/00
to
Funny I never really find anything good on their site either
In article <8s4gu8$ed2$1...@nnrp1.deja.com>,
0 new messages