Parsing.
Laszlo Lukoczki
Operating system: Windows 95 OSR2
Network: --Other--
Can you shed light on the following problem. Something recently
caused ACT to loose track of what portion of the contact field is the
"First name" field. When viewing records on a sorted Contact list, a
few contact entries appear not be in alphabatic order. One suspect
contact is highlighted, I then press F2, nothing is highlighted in
the First name field. To correct the problem I then highlight the
correct part of the First name field and press OK. That contact is
then correctly sorted. This problem only exists in one of our
databases.
We've been told this is known as a parsing problem, and it has caused
ACT to crash frequently. Fixing the problem takes time and causes
undue disruption. I would like to never expeirence the same problem
again. So could you please tell me why it happens and how can we stop
it happening in the furture?
Cheers,
Laszlo.
Chris Underwood [Symantec]
<xla...@mentor-systems.com> wrote:
Hello There,
One thing that you can do to help prevent this again, is to Compress
and Reindex the database on a weekly basis. If this is forgotten
etc., you can have database crashes. Another step that is real
important is to make a backup of the database on a regular basis.
Let me know if you have any further questions.
Chris Underwood [Symantec Corp.]
Please continue to post your messages to the public discussion groups
as Symantec does not provide support via private email.
If you have difficulty getting a response, please read the following
article:
http://service1.symantec.com/SUPPORT/sharedtech.nsf/docid/1998527114414
For free technical support newsletters, Knowledge Base support
articles, our Online Support Genie, and FAQs, visit our ACT! support
page:
http://www.symantec.com/techsupp/act.html
Laszlo Lukoczki
Operating system: Windows 95 OSR2
Network: --Other--
Thanks Chris,
We do take backups of our databases, and compress and reindex it on a
daily basis. The problem started when our main NT server crashed. It
holds the databases and networked shared copy of ACT. Since then the
databases have been compressed and reindexed, but ACT crashed (upto 3
times a day on a users PC) with an ACT.EXE error. This usually
happens when details are changed such as name, and is not restricted
to a single database. The parsing problem mentioned above seemed to
be the only visible result of the crash, but fixing this has not
cured the problem. Can you tell me what has happeneed to ACT to cause
it to crash more often and what can I do. Re-installing ACT on the NT
server is not easy as its very business critical machine.
Cheers,
Laszlo.
Laszlo Lukoczki
Laszlo Lukoczki
Chris Underwood [Symantec]
<xla...@mentor-systems.com> wrote:
>We do take backups of our databases, and compress and reindex it on a
>daily basis. The problem started when our main NT server crashed. It
>holds the databases and networked shared copy of ACT. Since then the
>databases have been compressed and reindexed, but ACT crashed (upto 3
>times a day on a users PC) with an ACT.EXE error. This usually
>happens when details are changed such as name, and is not restricted
>to a single database. The parsing problem mentioned above seemed to
>be the only visible result of the crash, but fixing this has not
>cured the problem. Can you tell me what has happeneed to ACT to cause
>it to crash more often and what can I do. Re-installing ACT on the NT
>server is not easy as its very business critical machine.
>
>Cheers,
>
>Laszlo.
Hello There,
One thing that you may want to also check out is the document on
sharing databases over NT. There is a knowledge base article that
covers this in detail in the ACT! Knowledge Base. You can use the
link that I have placed below in order to open this article.
Title: 'Sharing Databases on a Windows NT Server Keeps Corrupting the
Indexes'
Document ID: 1998223162925
Web URL:
http://service1.symantec.com/SUPPORT/act.nsf/docid/1998223162925
Brian Mr. Happy Tolman
The Usual Disclaimer: I am not affliated with Symantec in any way.
I'm just another ACT user.
On 25 Sep 1998 09:24:10 GMT Laszlo Lukoczki
<xla...@mentor-systems.com>'s said this in a message in the
symantec.support.win95.act3.database-issues newsgroup:
>Configuration Information:
> Operating system: Windows 95 OSR2
> Network: --Other--
>
>On Thu, 24 Sep 1998 14:17:23 GMT, Chris Underwood [Symantec] wrote:
>> On 23 Sep 1998 14:40:03 GMT, Laszlo Lukoczki
>> <xla...@mentor-systems.com> wrote:
>>
>> >Configuration Information:
>> > Operating system: Windows 95 OSR2
>> > Network: --Other--
>> >
>> >Can you shed light on the following problem. Something recently
>> >caused ACT to loose track of what portion of the contact field is the
>> >"First name" field. When viewing records on a sorted Contact list, a
>> >few contact entries appear not be in alphabatic order. One suspect
>> >contact is highlighted, I then press F2, nothing is highlighted in
>> >the First name field. To correct the problem I then highlight the
>> >correct part of the First name field and press OK. That contact is
>> >then correctly sorted. This problem only exists in one of our
>> >databases.
>> >
>> >We've been told this is known as a parsing problem, and it has caused
>> >ACT to crash frequently. Fixing the problem takes time and causes
>> >undue disruption. I would like to never expeirence the same problem
>> >again. So could you please tell me why it happens and how can we stop
>> >it happening in the furture?
>>
>> Hello There,
>>
>> One thing that you can do to help prevent this again, is to Compress
>> and Reindex the database on a weekly basis. If this is forgotten
>> etc., you can have database crashes. Another step that is real
>> important is to make a backup of the database on a regular basis.
>>
>> Let me know if you have any further questions.
>>
>> Chris Underwood [Symantec Corp.]
>>
>> Please continue to post your messages to the public discussion groups
>> as Symantec does not provide support via private email.
>>
>> If you have difficulty getting a response, please read the following
>> article:
>>
>> http://service1.symantec.com/SUPPORT/sharedtech.nsf/docid/1998527114414
>>
>> For free technical support newsletters, Knowledge Base support
>> articles, our Online Support Genie, and FAQs, visit our ACT! support
>> page:
>>
>> http://www.symantec.com/techsupp/act.html
>>
>
>Thanks Chris,
>
>We do take backups of our databases, and compress and reindex it on a
>daily basis. The problem started when our main NT server crashed. It
>holds the databases and networked shared copy of ACT. Since then the
>databases have been compressed and reindexed, but ACT crashed (upto 3
>times a day on a users PC) with an ACT.EXE error. This usually
>happens when details are changed such as name, and is not restricted
>to a single database. The parsing problem mentioned above seemed to
>be the only visible result of the crash, but fixing this has not
>cured the problem. Can you tell me what has happeneed to ACT to cause
>it to crash more often and what can I do. Re-installing ACT on the NT
>server is not easy as its very business critical machine.
>
>Cheers,
>
>Laszlo.
I had an attorney named Laszlo once...
You might consider looking into the setup of the user's workstations.
While the Symantec artical will allow you to set up the server, the
user's workstation *can* corrupt the database also.
See my page called "System Basics" - it should give you the idea of
what an ideal setup looks like:
http://www.undergroundact.com/system_basics.htm
Let me know if that helps ...
Brian Tolman
Underground ACT!
http://www.undergroundact.com
The Internet's Largest & Most Popular ACT! Site!
Site Content includes:
=====================================================================
| S3 Video fixes | Book lists | Links! |
=====================================================================
| Known Problems! | Reviews! | More Support |
=====================================================================
| Ron Madara's | David Brinely, | More Fixin's than |
| Holiday Calendar! | ACT! User!" | Momma's Kitchen |
=====================================================================
Stop by and see all the changes!
====================A=N=T=I==S=P=A=M==A=D=V=I=C=E====================
1. Forward all unsolicited commercial email to abuse@serviceprovider,
where "serviceprovider" is the ISP of the spammer.
2. Forward Any email that is a possible violation of US Code 18 to
fr...@uspis.gov.
3. Forward any email promising great rewards to All email promising
to the IRS, SEC, or the US Postal Inspector, whichever amuses
you more.
=====================================================================
Laszlo Lukoczki
We do take backups of our databases, and compress and reindex it on a
daily basis. The problem started when our main NT server crashed. It
holds the databases and networked shared copy of ACT. Since then the
databases have been compressed and reindexed, but ACT crashed (upto 3
times a day on a users PC) with an ACT.EXE error. This usually
happens when details are changed such as name, and is not restricted
to a single database. All our users use a workstation copy as ACT and
the correct version of VREDIR (4.00.1116). The parsing problem
mentioned above seemed to be the only visible result of the crash,
but fixing this has not cured the problem. Can you tell me what has
happeneed to ACT to cause it to crash more often and what can I do.
Re-installing ACT on the NT server is not easy as its very business
critical machine. Creating a new database is not a desired option as
we have a number of sync users, with sync packets waiting to go.
Cheers,
Laszlo.
Chris Underwood [Symantec]
<xla...@mentor-systems.com> wrote:
>Thanks Chris,
>
>We do take backups of our databases, and compress and reindex it on a
>daily basis. The problem started when our main NT server crashed. It
>holds the databases and networked shared copy of ACT. Since then the
>databases have been compressed and reindexed, but ACT crashed (upto 3
>times a day on a users PC) with an ACT.EXE error. This usually
>happens when details are changed such as name, and is not restricted
>to a single database. All our users use a workstation copy as ACT and
>the correct version of VREDIR (4.00.1116). The parsing problem
>mentioned above seemed to be the only visible result of the crash,
>but fixing this has not cured the problem. Can you tell me what has
>happeneed to ACT to cause it to crash more often and what can I do.
>Re-installing ACT on the NT server is not easy as its very business
>critical machine. Creating a new database is not a desired option as
>we have a number of sync users, with sync packets waiting to go.
Hello There,
I am not sure what else to recommend here short of a Uninstall and
Reinstall of the program. I would also recommend that you check out
the following article if you have not already. There is a knowledge
base article that covers this in detail in the ACT! Knowledge Base.
You can use the link that I have placed below in order to open this
article.
http://service1.symantec.com/SUPPORT/act.nsf/docid/1998223162925