Community
Showing results for 
Search instead for 
Do you mean 
Reply

Act 2009 Premium--Mystery dates self-populating

Tuned Listener
Posts: 10
Country: United States

Act 2009 Premium--Mystery dates self-populating

Hi all,

 

Have 2009 with the 11.1 update and Hotfix 1 & 2 installed on two databases with roughly dozen users on each database. No syncing/web access is being used. We run reports out of Crystal using the ACT Reader and have TopLine Designer installed.

 

We have customized the databased with many new fields, especially on the company records and have come across a problem where occasionally some date fields will auto-populate themselves--on a company record--with the current date. The weird part is that if the user changes to a different company record and then back to the first record (with the 'phantom' dates) the auto-populated dates disappear. This happens randomly in both databases with various users (I even have screen shots).

 

Both databases have weekly scheduled maintenance.

 

This has caused a lot of confusion for the users and makes my management suspect of the quality of our data.

 

Any ideas on what could be doing this? Can this be related to the .NET framework? Any direction to explore would be greatly appreciated.

 

Thanks.

-mark 

Tuned Listener
Posts: 10
Country: United States

Re: Act 2009 Premium--Mystery dates self-populating

Wanted to add that these dates appear in both empty date fields and in date fields that ALREADY have data, without actually overwriting the exist content. So, if you look at a company record with these false dates and then switch to another company record and then back to the original record the 'phantom' dates are gone and the correct dates appear in the field.

 

This is very frustrating.

Platinum Elite Contributor
Posts: 6,537
Country: USA

Re: Act 2009 Premium--Mystery dates self-populating

Hello mbudzyn,

The issue you are describing is a reported issue. It is essentially a display refresh issue with the GUI that causes "ghosted" data to display without actually changing the data. We have seen this most often in highly customized databases such as yours. When this happens, pressing the F5 button to refresh will usually correct the display. We are still investigating the cause of this issue to determine a solution. Some things that can be done on the individual machines that may help:

- Decrease/turn off hardware acceleration

- Update video drivers

- Disable non-essential graphics toys and display options

 

An update will be provided when additional information regarding this issue becomes available.

Greig Hollister

Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.

Tuned Listener
Posts: 10
Country: United States

Re: Act 2009 Premium--Mystery dates self-populating

Hi Greig

 

Thank you for validating our experiences with this issue; I'm glad to hear that it is a reported issue that is being investigated.

 

We'll try some of the recommendations.

 

Just to be clear: will the update be posted here in this thread?

 

Platinum Elite Contributor
Posts: 6,537
Country: USA

Re: Act 2009 Premium--Mystery dates self-populating

Normally the updates are either hot fixes or new builds, and we do post announcements for these in this forum.

Greig Hollister

Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.

New Member
Posts: 3
Country: Australia

Re: Act 2009 Premium--Mystery dates self-populating

Hi - we have ACT 11.1 and also have "ghosting" issues wih regard to dates.  If the current contact ghosts from the previous contact, then we move to any other contact, it doesn't just ghost it duplicates the date and holds it!  When we go back to the contact list view, the "stolen" data shows on the list too.  We have also had the contact screen showing a "ghosted" dated, but the contact list showing the original data.  We have screen dumps showing this.  We now have a situation where we don't know which contact has "stolen" data from another contact!.  As we use the database for critical date information, that is licence expiry dates etc. which affect our funding and compliance, we are now in a precarious position.  We don't know how many contact records have been affected, and which dates have been affected.  Each of 200 records of a particular contact group have 23 applicable dates, therefore we potentially have 4,200 entries that we don't know which are correct and which are not.  Very concerned that this issue hasn't received more recognition and support from SAGE.

julieG