code error after deleting a view - InfoPath Dev
in

InfoPath Dev

code error after deleting a view

Last post 03-13-2007 11:03 AM by Greg Collins. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 03-09-2007 10:56 AM

    • lou131
    • Top 100 Contributor
    • Joined on 02-13-2007
    • USA
    • Posts 89

    code error after deleting a view

    Hi,

    I have a form with 6 views and attempted to remove some. When I run the form in preview I get a code error.

    Why would I get a code error if the view has been removed. Is there some kind of maintenance that has to be run on the form after you remove a view?

    Thanks
    Lou
  • 03-12-2007 09:49 AM In reply to

    Re: code error after deleting a view

    Normally no.

    What is the error, have you checked around in your code to see if there was something specific to that view?
  • 03-12-2007 10:46 AM In reply to

    • lou131
    • Top 100 Contributor
    • Joined on 02-13-2007
    • USA
    • Posts 89

    Re: code error after deleting a view

    Hi,
    I resolved the issue deleting On Click functions in the On Load Event and that fixed the issue. I guess they stayed resident after the view was deleted.

    I'm going crazy trying to resolve performance issues on initial load. My form has 6 views and it takes 30 - 45 seconds to load. After load, switching views is fine. So I started deleted views and testing performance. Hence my issue that I posted below. Now that the code issue is resolved, I broke up my form into 3 separate template files and each still takes over 30 seconds to load.

    I have deadlines to meet and must get the form to load in 5 seconds or less. I'm pulling data from 4 data sources on a sharepoint site but they are rather small lists and I changed the field settings and tested in form preview with no improvement.

    Are there some code changes that I can make in the on load event that can speed up loading performance?
  • 03-13-2007 11:03 AM In reply to

    Re: code error after deleting a view

    Glad you got that part figured out. Code is not affected by designer changes--you have to keep that up-to-date manually.

    Try removing the onload code (or as much as possible) and see what difference that makes. Perhaps there is something very inefficient happening.

    Also, if you have any OnAfterChange events, make sure that those aren't getting called numerous times due to changes you might be making in the onload code. You can set a global flag (fInOnload = true) and then check for this in your other code to avoid processing things that don't need to be processed during that time.
Page 1 of 1 (4 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.