tag:beezwax.tenderapp.com,2010-10-12:/discussions/inspectorpro-5/2-inspectorpro-5Beezwax: Discussion 2015-12-04T17:59:30Ztag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-03-20T03:33:52Z2015-03-20T03:33:53ZInspectorPro 5<div><p>I am having some trouble with InspectorPro 5. I made several
attempts today to import DDRs which did not seem to import any
data. Previously I had about 4 or 5 solutions imported. After
attempting several times to import I managed to get one to import
properly. The next one I tried failed again. That is it seemed to
import but the import took only 16 seconds and all the records were
empty.</p>
<p>Also I am wondering when you might have some documentation on
your site that is specific to InspectorPro 5?</p></div>Heidi McMathtag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-03-20T05:53:51Z2015-03-20T05:53:51ZInspectorPro 5<div><p>It could be malformed XML, which sometimes FMP Advanced will
spit out in the DDR. One of our developers may want to see the DDR
(I'll find out).</p>
<p>But some things to check:<br>
Was the new solution import done from a DDR file in the same
location as the previous 4-5? Was that file named correctly?</p>
<p>How did that DDR file compare in size to the 4-5 previous?</p>
<p>Are you on Mac or Windows?</p></div>jay_gtag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-03-20T06:20:49Z2015-03-20T06:20:49ZInspectorPro 5<div><p>Heidi,</p>
<p>Can you send us the DDR and we’ll have a look at it.</p>
<p>Thanks</p>
<p>Vince</p></div>Vince Menannotag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-04-07T09:26:46Z2015-04-07T09:26:46ZInspectorPro 5<div><p>I had a similar product where no data were analyzed.<br>
My first DDR was placed on a network drive - then I created DDR on
my locale drive and problem solved.<br>
Is network drive the issue?</p></div>Søren Julegaardtag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-04-07T09:56:36Z2015-04-07T09:56:36ZInspectorPro 5<div><p>Heidi,</p>
<p>If you can send us your DDR we’ll take a look and see what
might be wrong.</p>
<p>Vince</p></div>Vince Menannotag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-04-07T10:08:03Z2015-04-07T10:08:04ZInspectorPro 5<div><p>Hi Vince<br>
No. 1 failed – no. 2 did OK</p>
<p>Venlig hilsen/Kind regards<br>
Søren Julegaard</p>
<p>Fra: Vince Menanno [mailto:<a href="mailto:tender+df61e3f479@tenderapp.com">tender+df61e3f479@tenderapp.com</a>]<br>
Sendt: 7. april 2015 11:57<br>
Til: Julegaard, Søren<br>
Emne: Re: InspectorPro 5 [InspectorPro 5 #2]</p></div>sjutag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-04-07T10:10:23Z2015-04-07T10:10:23ZInspectorPro 5<div><p>Søren,</p>
<p>These are just the summary files. What I need are the XML file
that got generated for each of your databases.</p>
<p>Vince</p></div>Vince Menannotag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-04-07T10:11:04Z2015-04-07T10:11:04ZInspectorPro 5<div><p>Søren,</p>
<p>What version of InspectorPro did this happen in and what
platform?</p>
<p>Are you using version 5?</p>
<p>And what platform?</p>
<p>Vince</p></div>Vince Menannotag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-06-02T20:36:20Z2015-06-02T21:00:30ZInspectorPro 5<div><p>I'm having the same issues: I have a DDR that when loaded into
IP5 only shows empty results, 0 records for everything. It only
took 13 seconds to import.</p>
<p>I have attached the summary and full XML files here. These were
generated by FMPA14.01 (perhaps that's the problem?).</p>
<p>I have an older DDR that I generated back in early May using
FMPA13.05 from this same database solution. That DDR imported just
fine. That DDR was also more than twice as large: ~25MB (FMPA13) vs
10MB (FMPA14). If anything more stuff was added to the file, not
deleted.</p>
<p>This is on OS X 10.9.5.</p>
<p>I just downloaded IP5 a few days ago from your website, using it
in trial mode.</p></div>justintag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-06-02T20:38:44Z2015-06-02T20:38:44ZInspectorPro 5<div><p>As for 14 support, the product page for IP5 doesn't mention it
specifically (for or against). There's a blog post, however, that
says it will work just fine.</p></div>justintag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-06-02T22:43:17Z2015-06-02T22:43:17ZInspectorPro 5<div><p>Hi there,</p>
<p>It seems that there is malformed XML.</p>
<p>In version 6 we’ll be able to better track that and fix
when we can… I attached a correct file.</p>
<p>Vince</p></div>Vince Menannotag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-06-02T22:53:48Z2015-06-02T23:20:21ZInspectorPro 5<div><p>It looks like it is the ampersand in the<br>
file name that throws it for a loop. Is that a general
XML<br>
problem or a FileMaker problem, or an IP5 problem? It's<br>
inside the double quotes so it seems like it would be safe.</p>
<p>-- Justin Close</p></div>justintag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-06-02T22:57:11Z2015-06-02T22:57:11ZInspectorPro 5<div><p>Justin,</p>
<p>It’s a FileMaker problem… basically if you have the
image. Re-insert it but change the name of the file. And you should
be good to go.</p>
<p>The “&” should be an encoded character.</p>
<p>Again we’ll address it better in the next release so to
this is a heads up for you as to what to do.</p>
<p>Vince</p></div>Vince Menannotag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-06-02T23:28:16Z2015-06-02T23:28:16ZInspectorPro 5<div><p>Thanks Vince, that fixed my problem.</p>
<p>There's are some interesting differences in the two files, from
FMPA13 v FMPA14:<br>
* the one from 14 is half the size (as noted) * the one from 13
reported fewer calculations (by 9 in this case) * the one from 13
reported many more dependencies overall ( about 1000)</p>
<p>See the screen shot: the top entry is from the fixed FMPA14
file, the lower is from FMPA13.05. These two DDRs were generated
from the same file, just using different versions of FileMaker.
Interesting.</p></div>justintag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-06-03T12:29:18Z2015-06-03T12:29:18ZInspectorPro 5<div><p>Justin,</p>
<p>I will also investigate this on my end thanks for the heads
up.</p>
<p>And glad it is working for you now</p>
<p>Vince</p></div>Vince Menannotag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-06-03T14:21:41Z2015-06-03T14:21:41ZInspectorPro 5<div><p>Justin,</p>
<p>Can you send me your 2 DDRs.</p>
<p>Thanks</p></div>Vince Menannotag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-06-03T15:17:10Z2015-06-03T15:17:10ZInspectorPro 5<div><p>I redid some exports just to make sure I was using the exact
same file state. The differences occurred again. I have attached
the two DDR sets. I have already edited the v14 file to remove the
problematic ampersand (well, I encoded it correctly instead of
removing it).</p>
<p>It is possible that the differences are caused by some v14
features; this DB does have a few uses of some placeholder text.
I'm not sure how the 13 export might handle that.</p></div>justintag:beezwax.tenderapp.com,2010-10-12:Comment/363306632015-06-03T15:33:55Z2015-06-03T15:33:55ZInspectorPro 5<div><p>Justin,</p>
<blockquote>
<p>On Jun 3, 2015, at 8:17 AM, justin <a href="mailto:tender+df61e3f479@tenderapp.com">tender+df61e3f479@tenderapp.com</a>
wrote: I redid some exports just to make sure I was using the exact
same file state. The differences occurred again. I have attached
the two DDR sets. I have already edited the v14 file to remove the
problematic ampersand (well, I encoded it correctly instead of
removing it).</p>
<p>It is possible that the differences are caused by some v14
features; this DB does have a few uses of some placeholder text.
I'm not sure how the 13 export might handle that.</p>
</blockquote>
<p>Yes that is possibly the case.</p>
<p>Vince</p></div>Vince Menanno