Re: [WebDNA] Integration with QuickBooks
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107071
interpreted = N
texte = --Apple-Mail=_7F77B35E-6F35-4E15-9877-AC74AC36A057Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=iso-8859-1Has anyone here taken a crack at using the Web Connector with QB? I'm =interested to see how webDNA can push data automatically to QB. It's =been a project on the back burner for a while.Not that long ago when I was researching QBXML, I found somewhere that =if you use QB to manage product/part inventory lists, importing orders =will not automatically deduct items from inventory like when you create =purchases from within QuickBooks. That may not be true across the =board, but the info I read claimed so, at least for the manufacturing =edition of QB. =20As Stuart said, you can export from QB, then open in text editor to see =how to format your own file for import. The thing I remember seeing, is =that though these files are tab-delimited, they have more than one field =declaration row. This could be tricky for exporting back to webDNA =application (if needed).On Jul 26, 2011, at 10:04 PM, Stuart Tremain wrote:> You can "read" a csv file but you can not read an xls file.>=20> Reading a csv file will involve doing a bit of cleaning and a bit of =fiddling to get the contents into a .db or [TABLE].>=20>=20> If you write the .csv file to the server and then [INCLUDE] it. This =is the best place to start to understand what you are getting from the =file and the best way to attack it.>=20>=20> On 27/07/2011, at 11:55 AM, sgbc cebu wrote:>=20>> Hi,>>=20>> Is there a way to remove WebDNA's restrictions of reading an xls or =csv database file.>>=20>> Thanks>>=20>> On Wed, Jul 27, 2011 at 7:28 AM, Stuart Tremain
=wrote:>> Very easy to do a manual export/import. Start by doing an export from =QuickBooks so that you know what need to be included when you export =from your web application.>>=20>>=20>> Regards>>=20>> Stuart Tremain>> IDFK Web Developments>> AUSTRALIA>> webdna@idfk.com.au>>=20>>=20>>=20>>=20>> On 27/07/2011, at 8:17 AM, Diane Blackmore wrote:>>=20>> > Hi>> >>> > Has anyone done any integration with Quickbooks using WebDNA, that =they're willing to share code on? I need a solution here that =preferrably doesn't use the Web Connector - I'd be happy with a straight =export as a .csv that can be imported into Quickbooks. Its an order that =needs to be imported, for existing clients, so there'd need to be a =one-to-many order/product relationship that is similar to the order file =structure of WebDNA.>> >>> > Cheers,>> >>> > >> >>>=20>> --------------------------------------------------------->> This message is sent to you because you are subscribed to>> the mailing list .>> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us>> Bug Reporting: support@webdna.us>>=20>> --------------------------------------------------------- This =message is sent to you because you are subscribed to the mailing list . =To unsubscribe, E-mail to: archives: =http://mail.webdna.us/list/talk@webdna.us Bug Reporting: =support@webdna.us>=20> --------------------------------------------------------- This message =is sent to you because you are subscribed to the mailing list . To =unsubscribe, E-mail to: archives: =http://mail.webdna.us/list/talk@webdna.us Bug Reporting: =support@webdna.us--Apple-Mail=_7F77B35E-6F35-4E15-9877-AC74AC36A057Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=iso-8859-1Has anyone here taken a crack at using the Web Connector with QB? = I'm interested to see how webDNA can push data automatically to =QB. It's been a project on the back burner for a =while.
Not that long ago when I was researching =QBXML, I found somewhere that if you use QB to manage product/part =inventory lists, importing orders will not automatically deduct items =from inventory like when you create purchases from within QuickBooks. = That may not be true across the board, but the info I read claimed =so, at least for the manufacturing edition of QB. =
As Stuart said, you can export from QB, =then open in text editor to see how to format your own file for import. = The thing I remember seeing, is that though these files are =tab-delimited, they have more than one field declaration row. This =could be tricky for exporting back to webDNA application (if =needed).
On Jul 26, 2011, =at 10:04 PM, Stuart Tremain wrote:
You can "read" a csv file but =you can not read an xls file.
Reading a csv file will =involve doing a bit of cleaning and a bit of fiddling to get the =contents into a .db or =[TABLE].
If you write the .csv =file to the server and then [INCLUDE] it. This is the best place to =start to understand what you are getting from the file and the best way =to attack it.
On 27/07/2011, at =11:55 AM, sgbc cebu wrote:
Hi,
Is there a way to remove WebDNA's restrictions =of reading an xls or csv database file.
Thanks
On Wed, Jul 27, 2011 at 7:28 AM, Stuart Tremain =
<webdna@idfk.com.au> =wrote:
Very easy =to do a manual export/import. Start by doing an export from QuickBooks =so that you know what need to be included when you export from your web =application.
Regards
Stuart Tremain
IDFK Web Developments
AUSTRALIA
webdna@idfk.com.au
On 27/07/2011, at 8:17 AM, Diane Blackmore wrote:
> Hi
>
> Has anyone done any integration with Quickbooks using WebDNA, that =they're willing to share code on? I need a solution here that =preferrably doesn't use the Web Connector - I'd be happy with a straight =export as a .csv that can be imported into Quickbooks. Its an order that =needs to be imported, for existing clients, so there'd need to be a =one-to-many order/product relationship that is similar to the order file =structure of WebDNA.
>
> Cheers,
>
> <EmailSignature_Diane.gif>
>
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/l=ist/talk@webdna.usBug Reporting: support@webdna.us
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/l=ist/talk@webdna.usBug Reporting: support@webdna.us
=--Apple-Mail=_7F77B35E-6F35-4E15-9877-AC74AC36A057--
Associated Messages, from the most recent to the oldest:
--Apple-Mail=_7F77B35E-6F35-4E15-9877-AC74AC36A057Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=iso-8859-1Has anyone here taken a crack at using the Web Connector with QB? I'm =interested to see how webDNA can push data automatically to QB. It's =been a project on the back burner for a while.Not that long ago when I was researching QBXML, I found somewhere that =if you use QB to manage product/part inventory lists, importing orders =will not automatically deduct items from inventory like when you create =purchases from within QuickBooks. That may not be true across the =board, but the info I read claimed so, at least for the manufacturing =edition of QB. =20As Stuart said, you can export from QB, then open in text editor to see =how to format your own file for import. The thing I remember seeing, is =that though these files are tab-delimited, they have more than one field =declaration row. This could be tricky for exporting back to webDNA =application (if needed).On Jul 26, 2011, at 10:04 PM, Stuart Tremain wrote:> You can "read" a csv file but you can not read an xls file.>=20> Reading a csv file will involve doing a bit of cleaning and a bit of =fiddling to get the contents into a .db or [table].>=20>=20> If you write the .csv file to the server and then [include] it. This =is the best place to start to understand what you are getting from the =file and the best way to attack it.>=20>=20> On 27/07/2011, at 11:55 AM, sgbc cebu wrote:>=20>> Hi,>>=20>> Is there a way to remove WebDNA's restrictions of reading an xls or =csv database file.>>=20>> Thanks>>=20>> On Wed, Jul 27, 2011 at 7:28 AM, Stuart Tremain =wrote:>> Very easy to do a manual export/import. Start by doing an export from =QuickBooks so that you know what need to be included when you export =from your web application.>>=20>>=20>> Regards>>=20>> Stuart Tremain>> IDFK Web Developments>> AUSTRALIA>> webdna@idfk.com.au>>=20>>=20>>=20>>=20>> On 27/07/2011, at 8:17 AM, Diane Blackmore wrote:>>=20>> > Hi>> >>> > Has anyone done any integration with Quickbooks using WebDNA, that =they're willing to share code on? I need a solution here that =preferrably doesn't use the Web Connector - I'd be happy with a straight =export as a .csv that can be imported into Quickbooks. Its an order that =needs to be imported, for existing clients, so there'd need to be a =one-to-many order/product relationship that is similar to the order file =structure of WebDNA.>> >>> > Cheers,>> >>> > >> >>>=20>> --------------------------------------------------------->> This message is sent to you because you are subscribed to>> the mailing list .>> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us>> Bug Reporting: support@webdna.us>>=20>> --------------------------------------------------------- This =message is sent to you because you are subscribed to the mailing list . =To unsubscribe, E-mail to: archives: =http://mail.webdna.us/list/talk@webdna.us Bug Reporting: =support@webdna.us>=20> --------------------------------------------------------- This message =is sent to you because you are subscribed to the mailing list . To =unsubscribe, E-mail to: archives: =http://mail.webdna.us/list/talk@webdna.us Bug Reporting: =support@webdna.us--Apple-Mail=_7F77B35E-6F35-4E15-9877-AC74AC36A057Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=iso-8859-1Has anyone here taken a crack at using the Web Connector with QB? = I'm interested to see how webDNA can push data automatically to =QB. It's been a project on the back burner for a =while.
Not that long ago when I was researching =QBXML, I found somewhere that if you use QB to manage product/part =inventory lists, importing orders will not automatically deduct items =from inventory like when you create purchases from within QuickBooks. = That may not be true across the board, but the info I read claimed =so, at least for the manufacturing edition of QB. =
As Stuart said, you can export from QB, =then open in text editor to see how to format your own file for import. = The thing I remember seeing, is that though these files are =tab-delimited, they have more than one field declaration row. This =could be tricky for exporting back to webDNA application (if =needed).
On Jul 26, 2011, =at 10:04 PM, Stuart Tremain wrote:
You can "read" a csv file but =you can not read an xls file.
Reading a csv file will =involve doing a bit of cleaning and a bit of fiddling to get the =contents into a .db or =
[table].
If you write the .csv =file to the server and then
[include] it. This is the best place to =start to understand what you are getting from the file and the best way =to attack it.
On 27/07/2011, at =11:55 AM, sgbc cebu wrote:
Hi,
Is there a way to remove WebDNA's restrictions =of reading an xls or csv database file.
Thanks
On Wed, Jul 27, 2011 at 7:28 AM, Stuart Tremain =
<webdna@idfk.com.au> =wrote:
Very easy =to do a manual export/import. Start by doing an export from QuickBooks =so that you know what need to be included when you export from your web =application.
Regards
Stuart Tremain
IDFK Web Developments
AUSTRALIA
webdna@idfk.com.au
On 27/07/2011, at 8:17 AM, Diane Blackmore wrote:
> Hi
>
> Has anyone done any integration with Quickbooks using WebDNA, that =they're willing to share code on? I need a solution here that =preferrably doesn't use the Web Connector - I'd be happy with a straight =export as a .csv that can be imported into Quickbooks. Its an order that =needs to be imported, for existing clients, so there'd need to be a =one-to-many order/product relationship that is similar to the
order file =structure of WebDNA.
>
> Cheers,
>
> <EmailSignature_Diane.gif>
>
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/l=ist/talk@webdna.usBug Reporting: support@webdna.us
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/l=ist/talk@webdna.usBug Reporting: support@webdna.us
=--Apple-Mail=_7F77B35E-6F35-4E15-9877-AC74AC36A057--
aaronmichaelmusic@gmail.com
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
NT beta ReadMe missing (b12-b15) (1997)
Exclamation (2002)
grep twice or a better way.... (2007)
errormessages.db (1997)
No Data Results (1997)
[WebDNA] Brian Harrington (2019)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
FireSite and PIXO (1998)
A quickie question (1997)
exclamation mark... (1999)
Emailer setup (1997)
allow or deny based on referer.... (1997)
quantity minimum problem (1997)
shipping costs (2000)
Bit off subject -- Faxing orders (1997)
Balancing randomness (2000)
How does WebCatalog search the database? (1997)
Supressing Error Messages (1998)
pop up menu's (1998)
[append] (1997)