11/22/2024 10:55:51 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss installing SalesLogix and general installation topics. View the code of conduct for posting guidelines.
|
|
|
|
Exception on Contact view, Windows 7 64 bit, slx 7.5.2
Posted: 29 Jul 10 7:24 AM
|
Hi all
i've recently installed slx 7.5.2 remote client, on a 64 bit Windows 7 laptop, and everything went smooth, i.e, can add/edit accounts, etc, except for one thing.
Everytime I open a contact, I receive the following error:
---------------------------
Function had an error...
---------------------------
An unusual error has occurred when executing View:Contacts. Contact your system administrator. 0x1 @0: Function View:Contacts Exception:
Exception EInvalidOperation:
Control '' has no parent window
Exception location:
[004C66CC]{SalesLogix.exe}
---------------------------
OK
---------------------------
---------------------------
Script Error
---------------------------
An error occurred executing active form script (Account:Contacts).
Error in include script (SYSTEM:SLX_COMMON): Control '' has no parent window at line 558, char 14.
---------------------------
OK
---------------------------
I've obviously copied the error straight from the message box.
Thanks in Advance!!! |
|
|
|
Re: Exception on Contact view, Windows 7 64 bit, slx 7.5.2
Posted: 01 Aug 10 9:25 AM
|
Your also have to apply all the Hot-Fixes for 7.5.2 - as there are many in there for 64bit issues. If you review the doc/pdf related to the hot-fix you will see whether it mentions 64bit. If so, apply it.
After you do this ,the problem will go away. |
|
|
|
Re: Exception on Contact view, Windows 7 64 bit, slx 7.5.2
Posted: 11 Aug 10 5:47 AM
|
I found a solution to my problem 
Firstly, it wasn't an environment issue, it was actually user specific (logged in on the main office server as the user, and received the same error, different environment)
Then to further prove it was user specific, i created another user, and used the problematic user as a template, and thus the new user had the same problem.
The solution was to delete all rows from the sysdba.useroptions table where the userid is equal to the problematic userid. and that sorted it out, error gone! |
|
|
| |
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|