I am having trouble storing beamed events from the regular Datebook application- why?
Most likely, you have your insert pointer in an event. If you do that, DateBk6 is not able to close the Datebook Database and since the regular Datebook application will grab the beamed event, it is not able to store the event (and rather curiously does not even bother to put up an error dialog indicating the problem!). Just tap elsewhere on the screen so that no item is currently selected and the beamed events will be received normally.
Most likely, you have your insert pointer in an event. If you do that, DateBk5 is not able to close the Datebook Database and since the regular Datebook application will grab the beamed event, it is not able to store the event (and rather curiously does not even bother to put up an error dialog indicating the problem!). Just tap elsewhere on the screen so that no item is currently selected and the beamed events will be received normally.
Most likely, you have your insert pointer in an event. If you do that, DateBk4 is not able to close the Datebook Database and since the regular Datebook application will grab the beamed event, it is not able to store the event (and rather curiously does not even bother to put up an error dialog indicating the problem!). Just tap elsewhere on the screen so that no item is currently selected and the beamed events will be received normally.
Related Questions
- If I need additional services above and beyond my regular subscription (special events, custom training, premium support, etc.), how will I be billed?
- I am having trouble storing beamed events from the regular Datebook application- why?
- What is a superdelegate and how do they differ from regular delegates?