10-08-2012 08:08 AM
Found resolve for 2013 premium Duplicate Checking Button no worky - - but now have another problem
Can't login to my 2013 "restored / updated databases" that I restored-as and updated into ACT!2013 Premium
Unable to Authenticate user etc... yada yada, etc..
yes I can open the demo db.
I can also create other 2013 databases and not be locked out. Anyway yesterday I was not locked out yet after created new 2013 db from older version of 2012 db..
I noticed in the knowledge base, that ACT2006 has this prob and a fix was made-
Is there one ready for ACT2013 yet please?
I went to knowledgebase and searched on 2013
Then also searched on more specific query suchas as 2013 Duplicate Check and found following resolve;
Below= the fix the the 2013 Duplicate Checking button problem is found in link below
I also noticed there is a fix for Report Probelms of ACT databases that get updated into ACT2013
I may need it as I can find the time to test it soon.
At this point I am considering running 2013 database fix tool
http://kb.sagesoftwareonline.com/app/answers/detail/a_id/30546/kw/2013/session/L3RpbWUvMTM0OTY0NTk4.... to see if it resolves mu ability to log into my databases ?
Should I wait for a 2013 Authentication fix? is there already a Fix? Help much appreciated. Cheers - FSB
10-09-2012 06:21 AM
Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.
10-09-2012 11:54 AM
Thanks for your response Greig,
I performed a ACT!2013 File/Restore db/Restore-as on one 2011 db and two 2012 db. On my win-7pro dell pc.
One db from act2011 and two of the db came from act2012wind-7pro. I used them all day doing various admin design layout things, closing and re-opening the database off and all day.
It is my standard issue login/pswd. there where a totla of 3 databases and I could only open one. The other two have the problem. I have not had time today to do further testing/recovery. hope to tomorrow. My 2013 customer had same issue on one of his db from me but in the end we deleted it and used another db from me(same build) and so far no more probs of this kind.
Best I recall it was one of the 2012 db's that I was still able to access next day. I will check back here and kb tomorrow b4 attempting further resolve. - Thank you - FSB