dbTalk Databases Forums  

XML export

comp.databases.filemaker comp.databases.filemaker


Discuss XML export in the comp.databases.filemaker forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Bob
 
Posts: n/a

Default XML export - 08-14-2010 , 06:59 PM






I'm having trouble with the XML export. It seems only capable of
exporting every single record in the database, whereas the other export
methods honour the existing found set.

Am I missing something obvious, or has Filemaker hosed us with the XML
export?

I seem to have no better luck with the List() function; no matter what I
do, the List function always returns ALL records for ONE of the join
parameters, rather than just the ones that are related as per the
relationship:

Let([

headerLine = "Issue Header";
list = List(siteIssuesURLdetails::c_URLxml)];
list & "<w:br/>"

)


returns ALL the URLs, ***NOT*** just the ones defined by the
siteIssuesURLdetails relationship.

I got around the latter by pre-computing the values with a script before
accessing the calculation fields that use them (which is BEYOND lame),
but some reason, I can't seem to get the [unstored] calculation field to
work properly:

Let([

headerLine = "Issue Header";
list = List(siteIssuesURLdetails::c_URLxml)];
list & "<w:br/>"

)

I have no idea why the XML export would work differently than the
others, or why the List() function would not consider the full context
of the siteIssuesURLdetails relationship (which is a 2 field equality:
table1::sideID == table2::sideID AND table1::issueID == table2::issueID.
For some reason, the List acts as if it were only table1::issueID ==
table2::issueID

Am I missing something fundamental, or has Filemaker just screwed up big
time?... again.

Reply With Quote
  #2  
Old   
Bob
 
Posts: n/a

Default Re: XML export - 08-14-2010 , 07:57 PM






I challenge ANYONE to prove that Filemaker is not a total piece of shit
by demonstrating how it can export ONLY FOUND RECORDS via XML.

WHAT KIND OF A GODDAMN PISS POOR EXCUSE FOR A DATABASE CAN'T EXPORT
SELECTED RECORDS?

WHAT A TOTAL PICE OF FUCKING CRAP, FILEMAKER, DON'T EVEN PRETEND THAT
THIS IS EVEN AN ENTRY LEVEL DATABASE. YOU SHOULD BE ASHAMED OF
YOURSELVES FOR SELLING SUCH A USELESS PIECE OF SHIT.

God forbid others should get tempted to use this hunk of crap, only
months later to determine that it can't even manage a BASIC EXPORT!

My GOD, Filemaker, how do you sell this shit with a straight face?!



In article
<bob-4DDAB9.16593814082010 (AT) newsfarm (DOT) iad.highwinds-media.com>,
Bob <bob (AT) example (DOT) com> wrote:

Quote:
I'm having trouble with the XML export. It seems only capable of
exporting every single record in the database, whereas the other export
methods honour the existing found set.

Am I missing something obvious, or has Filemaker hosed us with the XML
export?

I seem to have no better luck with the List() function; no matter what I
do, the List function always returns ALL records for ONE of the join
parameters, rather than just the ones that are related as per the
relationship:

Let([

headerLine = "Issue Header";
list = List(siteIssuesURLdetails::c_URLxml)];
list & "<w:br/>"

)


returns ALL the URLs, ***NOT*** just the ones defined by the
siteIssuesURLdetails relationship.

I got around the latter by pre-computing the values with a script before
accessing the calculation fields that use them (which is BEYOND lame),
but some reason, I can't seem to get the [unstored] calculation field to
work properly:

Let([

headerLine = "Issue Header";
list = List(siteIssuesURLdetails::c_URLxml)];
list & "<w:br/>"

)

I have no idea why the XML export would work differently than the
others, or why the List() function would not consider the full context
of the siteIssuesURLdetails relationship (which is a 2 field equality:
table1::sideID == table2::sideID AND table1::issueID == table2::issueID.
For some reason, the List acts as if it were only table1::issueID ==
table2::issueID

Am I missing something fundamental, or has Filemaker just screwed up big
time?... again.

Reply With Quote
  #3  
Old   
Your Name
 
Posts: n/a

Default Re: XML export - 08-14-2010 , 10:13 PM



In article <bob-7B1CB1.17575014082010 (AT) newsfarm (DOT) iad.highwinds-media.com>,
Bob <bob (AT) example (DOT) com> wrote:

Quote:
I challenge ANYONE to prove that Filemaker is not a total piece of shit
by demonstrating how it can export ONLY FOUND RECORDS via XML.

WHAT KIND OF A GODDAMN PISS POOR EXCUSE FOR A DATABASE CAN'T EXPORT
SELECTED RECORDS?

WHAT A TOTAL PICE OF FUCKING CRAP, FILEMAKER, DON'T EVEN PRETEND THAT
THIS IS EVEN AN ENTRY LEVEL DATABASE. YOU SHOULD BE ASHAMED OF
YOURSELVES FOR SELLING SUCH A USELESS PIECE OF SHIT.

God forbid others should get tempted to use this hunk of crap, only
months later to determine that it can't even manage a BASIC EXPORT!

My GOD, Filemaker, how do you sell this shit with a straight face?!
With this silly rant you've likely just written yourself off from getting
any help around here. \


Helpfull Harry )

Reply With Quote
  #4  
Old   
Howard Schlossberg
 
Posts: n/a

Default Re: XML export - 08-14-2010 , 10:19 PM



On 8/14/2010 4:59 PM, Bob wrote:
Quote:
I'm having trouble with the XML export. It seems only capable of
exporting every single record in the database, whereas the other export
methods honour the existing found set.

Am I missing something obvious, or has Filemaker hosed us with the XML
export?

I seem to have no better luck with the List() function; no matter what I
do, the List function always returns ALL records for ONE of the join
parameters, rather than just the ones that are related as per the
relationship:

Here's what I've learned from your post: you are using a faulty
relationship. Does the relationship display properly through a portal?
The List() function and the export do all respect the current
relationship, so if you are seeing something otherwise, it is not
FileMaker's fault. You need to take a deeper look at your relationship
and its key fields.

Reply With Quote
  #5  
Old   
Bob
 
Posts: n/a

Default Re: XML export - 08-14-2010 , 11:17 PM



Howard, you're totally with me... YES, through a relationhip it works
petfectly, it's only through the LIST or double loop Related Record that
things blow up... i.e. the preferred mechanism, or the failed work
around, they DON'T respect the relationship, or I wouldn't have bothered
you folks.

I've been working in FM since 1.0, I'm no slouch... this just doesn't
work.


In article <i47mb2$sj8$2 (AT) news (DOT) motzarella.org>,
Howard Schlossberg <howard (AT) nospam (DOT) fmprosolutions.com> wrote:

Quote:
On 8/14/2010 4:59 PM, Bob wrote:
I'm having trouble with the XML export. It seems only capable of
exporting every single record in the database, whereas the other export
methods honour the existing found set.

Am I missing something obvious, or has Filemaker hosed us with the XML
export?

I seem to have no better luck with the List() function; no matter what I
do, the List function always returns ALL records for ONE of the join
parameters, rather than just the ones that are related as per the
relationship:


Here's what I've learned from your post: you are using a faulty
relationship. Does the relationship display properly through a portal?
The List() function and the export do all respect the current
relationship, so if you are seeing something otherwise, it is not
FileMaker's fault. You need to take a deeper look at your relationship
and its key fields.

Reply With Quote
  #6  
Old   
Bob
 
Posts: n/a

Default Re: XML export - 08-14-2010 , 11:18 PM



In article
<your.name-1508101513560001 (AT) 203-109-171-237 (DOT) dial.dyn.ihug.co.nz>,
your.name (AT) isp (DOT) com (Your Name) wrote:

Quote:
In article <bob-7B1CB1.17575014082010 (AT) newsfarm (DOT) iad.highwinds-media.com>,
Bob <bob (AT) example (DOT) com> wrote:

I challenge ANYONE to prove that Filemaker is not a total piece of shit
by demonstrating how it can export ONLY FOUND RECORDS via XML.

WHAT KIND OF A GODDAMN PISS POOR EXCUSE FOR A DATABASE CAN'T EXPORT
SELECTED RECORDS?

WHAT A TOTAL PICE OF FUCKING CRAP, FILEMAKER, DON'T EVEN PRETEND THAT
THIS IS EVEN AN ENTRY LEVEL DATABASE. YOU SHOULD BE ASHAMED OF
YOURSELVES FOR SELLING SUCH A USELESS PIECE OF SHIT.

God forbid others should get tempted to use this hunk of crap, only
months later to determine that it can't even manage a BASIC EXPORT!

My GOD, Filemaker, how do you sell this shit with a straight face?!

With this silly rant you've likely just written yourself off from getting
any help around here. \


Helpfull Harry )

ah, that's the bullshit response I expected from people running a system
that doesn't actually work. unless you can ACTUALLY export XML for only
current records.

FMP is a bullshit product. prove me wrong.

Reply With Quote
  #7  
Old   
Your Name
 
Posts: n/a

Default Re: XML export - 08-15-2010 , 12:41 AM



"Bob" <bob (AT) example (DOT) com> wrote

Quote:
In article
your.name-1508101513560001 (AT) 203-...dyn.ihug.co.nz>,
your.name (AT) isp (DOT) com (Your Name) wrote:

In article <bob-7B1CB1.17575014082010 (AT) newsfarm (DOT) iad.highwinds-media.com>,
Bob <bob (AT) example (DOT) com> wrote:

I challenge ANYONE to prove that Filemaker is not a total piece of
shit
by demonstrating how it can export ONLY FOUND RECORDS via XML.

WHAT KIND OF A GODDAMN PISS POOR EXCUSE FOR A DATABASE CAN'T EXPORT
SELECTED RECORDS?

WHAT A TOTAL PICE OF FUCKING CRAP, FILEMAKER, DON'T EVEN PRETEND THAT
THIS IS EVEN AN ENTRY LEVEL DATABASE. YOU SHOULD BE ASHAMED OF
YOURSELVES FOR SELLING SUCH A USELESS PIECE OF SHIT.

God forbid others should get tempted to use this hunk of crap, only
months later to determine that it can't even manage a BASIC EXPORT!

My GOD, Filemaker, how do you sell this shit with a straight face?!

With this silly rant you've likely just written yourself off from
getting
any help around here. \


Helpfull Harry )


ah, that's the bullshit response I expected from people running a system
that doesn't actually work. unless you can ACTUALLY export XML for only
current records.

FMP is a bullshit product. prove me wrong.

Reply With Quote
  #8  
Old   
Your Name
 
Posts: n/a

Default Re: XML export - 08-15-2010 , 12:43 AM



"Bob" <bob (AT) example (DOT) com> wrote

Quote:
In article
your.name-1508101513560001 (AT) 203-...dyn.ihug.co.nz>,
your.name (AT) isp (DOT) com (Your Name) wrote:

In article <bob-7B1CB1.17575014082010 (AT) newsfarm (DOT) iad.highwinds-media.com>,
Bob <bob (AT) example (DOT) com> wrote:

I challenge ANYONE to prove that Filemaker is not a total piece of
shit
by demonstrating how it can export ONLY FOUND RECORDS via XML.

WHAT KIND OF A GODDAMN PISS POOR EXCUSE FOR A DATABASE CAN'T EXPORT
SELECTED RECORDS?

WHAT A TOTAL PICE OF FUCKING CRAP, FILEMAKER, DON'T EVEN PRETEND THAT
THIS IS EVEN AN ENTRY LEVEL DATABASE. YOU SHOULD BE ASHAMED OF
YOURSELVES FOR SELLING SUCH A USELESS PIECE OF SHIT.

God forbid others should get tempted to use this hunk of crap, only
months later to determine that it can't even manage a BASIC EXPORT!

My GOD, Filemaker, how do you sell this shit with a straight face?!

With this silly rant you've likely just written yourself off from
getting
any help around here. \

ah, that's the bullshit response I expected from people running a system
that doesn't actually work. unless you can ACTUALLY export XML for only
current records.

FMP is a bullshit product. prove me wrong.
Ranting and raving like an idiot automatically puts you on my "don't bother
with" list ... to quote the rather silly TV show: You are the weakest link,
goodbye. \

Helpfull Harry )

Reply With Quote
  #9  
Old   
Your Name
 
Posts: n/a

Default Re: XML export - 08-15-2010 , 04:13 PM



"Peter" <peter (AT) mailinator (DOT) com> wrote

Quote:
I'd also be interested in knowing how others on the list manage to
share code... copying and pasting from script to script is awesome, but
there does not seem to be a way to grab a textual representation.
Scripts put into the Newsgroup messages are rarely very long. I simply type
the sample code directly into the newsreader (which of course means there
may well be occasinal typos).

You can print the Script to a PDF (or text file using an appropriate
"printer" driver) and then copy the text from there.

Helpfull Harry )

Reply With Quote
  #10  
Old   
Jens Teich
 
Posts: n/a

Default Re: XML export - 08-16-2010 , 03:54 PM



"Your Name" <your.name (AT) isp (DOT) com> writes:

Quote:
"Peter" <peter (AT) mailinator (DOT) com> wrote in message
news:2010081510073316807-peter (AT) mailinatorcom (DOT) ..

I'd also be interested in knowing how others on the list manage to
share code... copying and pasting from script to script is awesome, but
there does not seem to be a way to grab a textual representation.

Scripts put into the Newsgroup messages are rarely very long. I simply type
the sample code directly into the newsreader (which of course means there
may well be occasinal typos).

You can print the Script to a PDF (or text file using an appropriate
"printer" driver) and then copy the text from there.
If I need a script as text I copy it from database design report (DDR of FMPA)

Jens

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.