Most Tricky Issue Contest - Win the Prize!

[Rus]

It's been a couple of weeks since Pivotal CRM Forum was launched and now we seem to have a few members in our community.

To encourage knowledge exchange and introduce our members to each other we announce the Most Tricky Issue Contest.

Members are invited to describe tricky issues they struggled with for others to propose solutions.

As soon as we have enough issues to choose from we will start a poll to decide on the trickiest issue.

The winner will get the prize - a $100 gift certificate from Amazon.com!

[shicklin]

Problem:
Need to identify companies that form a loop using the Parent Company Field.

e.g.  Company A links to Company B, Company B links to Company C, Company C links to Company X, Company X links to Company A

How to identify Company A when there could be x links in the chain

[RLD_developer]

Hello, the Amazon voucher is as good as mine!! (here goes...)

We are currently running Pivtotal cms version 3.0 (our system has been customised that much we cannot get enough down time to upgrade to 5.7).  I make a call via an Active Form call / Appserver rule to a VB dll that connects to the ED via an Active Access connection (we are running WA).  the dll forces a new record to be added via an active form and returns the ID generated. 

The reason the record is added via the dll is because it is also used for our web site and this was data integrity is maintained as there is only one method to create a new booking record.  The problem is that the instantiated user and the middle teir logged in user both has permission to the table / everything and when the AA form is attempted to open "unable to get form data" error message is returned - does anyone know why / have you encountered anything like this in the past?

Any help would be greatly appreciated as this functionality is supposed to be released next Thursday (1/6/06)... 

[CougarSoftware]

In windows access, how do you force a prompt with only one exit on it (i.e. an "OK"-only prompt) to pop up and _stay_ on top of the form? It appears that if the prompt only has one exit point, the agent proceeds to execute past the prompt, and often the form is brought into focus in front of the prompt. Needless to say, this introduces quite a bit of confusion, especially with not very technically savvy users.

[jaybee]

In windows access, how do you force a prompt with only one exit on it (i.e. an "OK"-only prompt) to pop up and _stay_ on top of the form? It appears that if the prompt only has one exit point, the agent proceeds to execute past the prompt, and often the form is brought into focus in front of the prompt. Needless to say, this introduces quite a bit of confusion, especially with not very technically savvy users.

The only way to get a modal prompt is to use a form with a text field (ie txt_message) where you can dynamically move your prompt message.
With a Pivotal Agent , define the Setfocus command on exit of this text field.
Call your process. Then use a close with no warning command to close your fake prompt.

Hope this helps....

[Rus]

The poll is now closed and the winner is Steve Hicklin.

Attached is the picture of Steve receiving the award.

Well done Steve!

Will you please post the solution?

[kwiecin]

Congratulations Steve!!!

[tdelios]

In windows access, how do you force a prompt with only one exit on it (i.e. an "OK"-only prompt) to pop up and _stay_ on top of the form? It appears that if the prompt only has one exit point, the agent proceeds to execute past the prompt, and often the form is brought into focus in front of the prompt. Needless to say, this introduces quite a bit of confusion, especially with not very technically savvy users.

if you have the shortcut of the form component BEFORE the prompt component, then the situation that you mentioned will occur..  the agent will sit there and pause until the 'ok' button on the prompt has been clicked.  The only time I see this as a problem is either the prompt was on the screen, but the user has clicked on something else to hide the prompt in the background..  I have also seen that agents 'call' other agents and not realize it that caused something else to be invoked before the prompt component was hit.