RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6

This WebDNA talk-list message is from

2020


It keeps the original formatting.
numero = 115018
interpreted = N
texte = 2646 This is a multipart message in MIME format. ------=_NextPart_000_00FD_01D5E70F.0ABEF4B0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Stuart, =20 Code wise =E2=80=A6you are right =E2=80=A6I see nothing wrong. I = replicated in on our FastCGI WebDNA Win2012R2 boxes =E2=80=A6no issue = works fine and gets saved as well (via jQuery Ajax). =20 Will try it on our Linux box later to see if the same occurs as per = yours. =20 Here is something you may want to try =E2=80=A6.use = [replacefounditems] =20 It may work around the issue in the interim till the mystery is = resolved. Another method is to set up a [table] in your admin-switch.dna = =E2=80=A6collect and store the incoming variables there =E2=80=A6.then = do the [replace] from the stored [table] data to see if that helps. = Incidentally =E2=80=A6having the [table] there will help shorten the = post url string as you can manual have it in the table as default if = needed. =20 Just to confirm =E2=80=A6once the Ajax runs the call =E2=80=A6.variable = gets to the landing page =E2=80=A6data is updated in RAM but not in DB. = Could you write a file output after the replace to see if the file = generated has the variable value, since you are saying that the system = is not seeing the variable when called upon by another page and only = after Admin Flush it appears. =20 Cheers Terry Nair WhatsApp / Mob : +65 9672 9540 =20 From: talk@webdna.us =20 Sent: Wednesday, February 19, 2020 09:32 AM To: WebDNA Talk List Subject: Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI = version 8.6 =20 Hi Terry =20 It is hard to work out who sent email to the list now that the = =E2=80=9Cfrom" has changed. =20 =20 The call is very simple, a url with variables.=20 =20 =20 admin-switch.dna?task=3Dswitch-6&dbid=3D6&dbidname=3DSM-ID&dbname=3Dshipp= ingmethods&dbfield=3DSM-ACTIVE&active=3DT =20 =20 The receiving page is very simple too. [REPLACE = db=3D../data/[DBNAME].db&eq[DBIDNAME]datarq=3D[DBID]&max=3D1][!] [/!][DBFIELD]=3D[URL][DBVALUE][/URL][!] [/!][/REPLACE] =20 =20 The replace is 100% correct in the db file if I open it up, the problem = is that until I manually flush the dbs it is not recognised. =20 I have tried putting in [CLOSEDATABASE db=3D../data/[DBNAME].db] or = [COMMITDATABASE db=3D../data/[DBNAME].db] or even [FLUSHDATABASES] with = no resolution. =20 It is not the one db, I have another ajax update for another db which = has the same issue. I have not gone through the entire system checking = for others. =20 Kind regards =20 Stuart Tremain Pharoah Lane Software AUSTRALIA webdna@plsoftware.com.au =20 =20 =20 =20 =20 =20 On 19 Feb 2020, at 12:11, talk@webdna.us wrote: =20 Morning Stuart, =20 You mentioned =E2=80=9CI have include [FLUSHDATABASES] in the ajax = call=E2=80=9D =E2=80=A6.am I correct to say that you are either doing a = GET or POST Ajax call to a file sitting on the server that has the tags = to execute the flush webdna tag? =20 If so =E2=80=A6can share the ajax call script and the page called by it = so that I can try to assist you. It is indeed strange that the change is = stored in RAM but not committed into the DB even with all the settings = you mentioned. Regardless =E2=80=A6after the update, the uncommitted = change should still be showing up when called upon by other pages = relying on it. =20 Cheers TDn =20 From: talk@webdna.us >=20 Sent: Wednesday, February 19, 2020 07:39 AM To: WebDNA Talk List > Subject: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version = 8.6 =20 I am having an issue with a couple of dbs. =20 Permissions are correct 775 Ownership is correct www-data:www-data =20 I am updating the db with an ajax call, I open the db ofter it has been = modified and the mod is there in the db. =20 The ajax call does a replace on the db. =20 There is no error reported from the ajax call. The WebDNA preference is "Automatically commit databases to disk after = modification" =20 The problem is that another page on the site is dependant on the new = value. This new value is not being found. =20 I have include [FLUSHDATABASES] in the ajax call to force the db to = clear however it is still not finding the new value. =20 If I use the WebDNA admin to [FLUSHDATABASES] then the page finds the = new value. =20 Any ideas ? =20 Kind regards =20 Stuart Tremain Pharoah Lane Software AUSTRALIA webdna@plsoftware.com.au =20 =20 =20 =20 =20 =20 =20 --------------------------------------------------------- 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://www.webdna.us/page.dna?numero=3D55 Bug Reporting: = support@webdna.us =20 --------------------------------------------------------- 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://www.webdna.us/page.dna?numero=3D55 Bug Reporting: = support@webdna.us =20 --------------------------------------------------------- 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://www.webdna.us/page.dna?numero=3D55 Bug Reporting: = support@webdna.us =20 ------=_NextPart_000_00FD_01D5E70F.0ABEF4B0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi = Stuart,

 

Code wise = =E2=80=A6you are right =E2=80=A6I see nothing wrong. I replicated in on = our FastCGI WebDNA Win2012R2 boxes =E2=80=A6no issue works fine and gets = saved as well (via jQuery Ajax).

 

Will try it = on our Linux box later to see if the same occurs as per = yours.

 

Here is = something you may want to try =E2=80=A6.use [rep= lacefounditems]

 

It may work = around the issue in the interim till the mystery is resolved. Another = method is to set up a [table] in your admin-switch.dna =E2=80=A6collect = and store the incoming variables there =E2=80=A6.then do the [replace] = from the stored [table] data to see if that helps. Incidentally = =E2=80=A6having the [table] there will help shorten the post url string = as you can manual have it in the table as default if = needed.

 

Just to = confirm =E2=80=A6once the Ajax runs the call =E2=80=A6.variable gets to = the landing page =E2=80=A6data is updated in RAM but not in DB. Could = you write a file output after the replace to see if the file generated = has the variable value, since you are saying that the system is not = seeing the variable when called upon by another page and only after = Admin Flush it appears.

 

Cheers

Terry = Nair

WhatsApp / = Mob : +65 9672 9540

 

From:<= /b> = talk@webdna.us <talk@webdna.us>
Sent: Wednesday, = February 19, 2020 09:32 AM
To: WebDNA Talk List = <talk@webdna.us>
Subject: Re: [WebDNA] COMMITDATABASE in = linux unix 64bits FastCGI version = 8.6

 

Hi = Terry

 

It is hard to work out who sent email to the =  list now that the =E2=80=9Cfrom" has = changed.

 

 

The call is very simple, a url with = variables. 

 

 

admin-switch.dna?task=3Dswitch-6&dbid=3D6&dbidn= ame=3DSM-ID&dbname=3Dshippingmethods&dbfield=3DSM-ACTIVE&acti= ve=3DT

 

 

The receiving page is very = simple too.



[REPLACE = db=3D../data/[DBNAME].db&eq[DBIDNAME]datarq=3D[DBID]&max=3D1][!]<= o:p>

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 [/!][DBFIELD]=3D[URL][DBVALUE][/URL][!]<= /span>

[/!][/REPLACE]

 

 

The replace is 100% correct in the db file if I open = it up, the problem is that until I manually flush the dbs it is not = recognised.

 

I = have tried putting in [CLOSEDATABASE db=3D../data/[DBNAME].db] = or [COMMITDATABASE db=3D../data/[DBNAME].db] or even = [FLUSHDATABASES] with no resolution.

 

It is not the one db, I have another ajax update for = another db which has the same issue. I have not gone through the entire = system checking for others.

 

Kind = regards

 

Stuart = Tremain

Pharoah Lane = Software

AUSTRALIA

 

 

 

 

 



On 19 Feb 2020, at 12:11, talk@webdna.us = wrote:

 

Morning = Stuart,

 =

You = mentioned =E2=80=9CI have include [FLUSHDATABASES] in the ajax = call=E2=80=9D = =E2=80=A6.am I correct to say that you are either doing a GET or POST = Ajax call to a file sitting on the server that has the tags to execute = the flush webdna tag?

 =

If so = =E2=80=A6can share the ajax call script and the page called by it so = that I can try to assist you. It is indeed strange that the change is = stored in RAM but not committed into the DB even with all the settings = you mentioned. Regardless =E2=80=A6after the update, the uncommitted = change should still be showing up when called upon by other pages = relying on it.

 =

Cheers = TDn

 =

From:<= /b> = talk@webdna.us <talk@webdna.us> 
Sent: Wednesday, February 19, 2020 = 07:39 AM
To: WebDNA Talk List <talk@webdna.us>
Subject:<= span class=3Dapple-converted-space> 
[WebDNA] COMMITDATABASE = in linux unix 64bits FastCGI version = 8.6

 

I = am having an issue with a couple of = dbs.

 

Permissions are correct = 775

Ownership = is correct www-data:www-data

 

I am updating the db with an ajax call, I open the db = ofter it has been modified and the mod is there in the = db.

 

The ajax call does a replace on the = db.

 

There is no error reported from the ajax = call.




The WebDNA preference is "Automatically commit = databases to disk after = modification"

 

The problem is that another page on the site is = dependant on the new value. This new value is not being = found.

 

I have include [FLUSHDATABASES] in the ajax call to = force the db to clear however it is still not finding the new = value.

 

If I use the WebDNA admin to [FLUSHDATABASES] then the = page finds the new value.

 

Any ideas ?

 

Kind = regards

 

Stuart Tremain

Pharoah Lane = Software

AUSTRALIA

 

 

 

 

 

 

-------------------------------------------------------= -- 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://www.webdna.us/p= age.dna?numero=3D55 Bug Reporting: support@webdna.us

------------= --------------------------------------------- This message is sent to = you because you are subscribed to the mailing list talk@webdna.= us To = unsubscribe, E-mail to: talk-leave@w= ebdna.us archives: http://www.w= ebdna.us/page.dna?numero=3D55 Bug = Reporting: support@webd= na.us

 

-------------------------------------------------------= -- 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://www.webdna.us/p= age.dna?numero=3D55 Bug Reporting: support@webdna.us

--------------------------------------------------------- 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://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us ------=_NextPart_000_00FD_01D5E70F.0ABEF4B0-- . Associated Messages, from the most recent to the oldest:

    
  1. RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 ("Terry Nair" 2020)
  2. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
  3. RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 ("Terry Nair" 2020)
  4. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Donovan Brooke 2020)
  5. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
  6. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Donovan Brooke 2020)
  7. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
  8. RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 ("Scott @ Itsula" 2020)
  9. RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 ("Scott @ Itsula" 2020)
  10. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
  11. RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 ("Scott @ Itsula" 2020)
  12. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
  13. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
  14. RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 ("Scott @ Itsula" 2020)
  15. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Brian Fries 2020)
  16. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Jym Duane 2020)
  17. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
  18. RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 ("Terry Nair" 2020)
  19. Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 (Stuart Tremain 2020)
  20. RE: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version 8.6 ("Terry Nair" 2020)
2646 This is a multipart message in MIME format. ------=_NextPart_000_00FD_01D5E70F.0ABEF4B0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Stuart, =20 Code wise =E2=80=A6you are right =E2=80=A6I see nothing wrong. I = replicated in on our FastCGI WebDNA Win2012R2 boxes =E2=80=A6no issue = works fine and gets saved as well (via jQuery Ajax). =20 Will try it on our Linux box later to see if the same occurs as per = yours. =20 Here is something you may want to try =E2=80=A6.use = [replacefounditems] =20 It may work around the issue in the interim till the mystery is = resolved. Another method is to set up a [table] in your admin-switch.dna = =E2=80=A6collect and store the incoming variables there =E2=80=A6.then = do the [replace] from the stored [table] data to see if that helps. = Incidentally =E2=80=A6having the [table] there will help shorten the = post url string as you can manual have it in the table as default if = needed. =20 Just to confirm =E2=80=A6once the Ajax runs the call =E2=80=A6.variable = gets to the landing page =E2=80=A6data is updated in RAM but not in DB. = Could you write a file output after the replace to see if the file = generated has the variable value, since you are saying that the system = is not seeing the variable when called upon by another page and only = after Admin Flush it appears. =20 Cheers Terry Nair WhatsApp / Mob : +65 9672 9540 =20 From: talk@webdna.us =20 Sent: Wednesday, February 19, 2020 09:32 AM To: WebDNA Talk List Subject: Re: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI = version 8.6 =20 Hi Terry =20 It is hard to work out who sent email to the list now that the = =E2=80=9Cfrom" has changed. =20 =20 The call is very simple, a url with variables.=20 =20 =20 admin-switch.dna?task=3Dswitch-6&dbid=3D6&dbidname=3DSM-ID&dbname=3Dshipp= ingmethods&dbfield=3DSM-ACTIVE&active=3DT =20 =20 The receiving page is very simple too. [REPLACE = db=3D../data/[DBNAME].db&eq[DBIDNAME]datarq=3D[DBID]&max=3D1][!] [/!][DBFIELD]=3D[url][DBVALUE][/URL][!] [/!][/REPLACE] =20 =20 The replace is 100% correct in the db file if I open it up, the problem = is that until I manually flush the dbs it is not recognised. =20 I have tried putting in [CLOSEDATABASE db=3D../data/[DBNAME].db] or = [COMMITDATABASE db=3D../data/[DBNAME].db] or even [flushdatabases] with = no resolution. =20 It is not the one db, I have another ajax update for another db which = has the same issue. I have not gone through the entire system checking = for others. =20 Kind regards =20 Stuart Tremain Pharoah Lane Software AUSTRALIA webdna@plsoftware.com.au =20 =20 =20 =20 =20 =20 On 19 Feb 2020, at 12:11, talk@webdna.us wrote: =20 Morning Stuart, =20 You mentioned =E2=80=9CI have include [flushdatabases] in the ajax = call=E2=80=9D =E2=80=A6.am I correct to say that you are either doing a = GET or POST Ajax call to a file sitting on the server that has the tags = to execute the flush webdna tag? =20 If so =E2=80=A6can share the ajax call script and the page called by it = so that I can try to assist you. It is indeed strange that the change is = stored in RAM but not committed into the DB even with all the settings = you mentioned. Regardless =E2=80=A6after the update, the uncommitted = change should still be showing up when called upon by other pages = relying on it. =20 Cheers TDn =20 From: talk@webdna.us >=20 Sent: Wednesday, February 19, 2020 07:39 AM To: WebDNA Talk List > Subject: [WebDNA] COMMITDATABASE in linux unix 64bits FastCGI version = 8.6 =20 I am having an issue with a couple of dbs. =20 Permissions are correct 775 Ownership is correct www-data:www-data =20 I am updating the db with an ajax call, I open the db ofter it has been = modified and the mod is there in the db. =20 The ajax call does a replace on the db. =20 There is no error reported from the ajax call. The WebDNA preference is "Automatically commit databases to disk after = modification" =20 The problem is that another page on the site is dependant on the new = value. This new value is not being found. =20 I have include [flushdatabases] in the ajax call to force the db to = clear however it is still not finding the new value. =20 If I use the WebDNA admin to [flushdatabases] then the page finds the = new value. =20 Any ideas ? =20 Kind regards =20 Stuart Tremain Pharoah Lane Software AUSTRALIA webdna@plsoftware.com.au =20 =20 =20 =20 =20 =20 =20 --------------------------------------------------------- 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://www.webdna.us/page.dna?numero=3D55 Bug Reporting: = support@webdna.us =20 --------------------------------------------------------- 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://www.webdna.us/page.dna?numero=3D55 Bug Reporting: = support@webdna.us =20 --------------------------------------------------------- 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://www.webdna.us/page.dna?numero=3D55 Bug Reporting: = support@webdna.us =20 ------=_NextPart_000_00FD_01D5E70F.0ABEF4B0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi = Stuart,

 

Code wise = =E2=80=A6you are right =E2=80=A6I see nothing wrong. I replicated in on = our FastCGI WebDNA Win2012R2 boxes =E2=80=A6no issue works fine and gets = saved as well (via jQuery Ajax).

 

Will try it = on our Linux box later to see if the same occurs as per = yours.

 

Here is = something you may want to try =E2=80=A6.use [rep= lacefounditems]

 

It may work = around the issue in the interim till the mystery is resolved. Another = method is to set up a [table] in your admin-switch.dna =E2=80=A6collect = and store the incoming variables there =E2=80=A6.then do the [replace] = from the stored [table] data to see if that helps. Incidentally = =E2=80=A6having the [table] there will help shorten the post url string = as you can manual have it in the table as default if = needed.

 

Just to = confirm =E2=80=A6once the Ajax runs the call =E2=80=A6.variable gets to = the landing page =E2=80=A6data is updated in RAM but not in DB. Could = you write a file output after the replace to see if the file generated = has the variable value, since you are saying that the system is not = seeing the variable when called upon by another page and only after = Admin Flush it appears.

 

Cheers

Terry = Nair

WhatsApp / = Mob : +65 9672 9540

 

From:<= /b> = talk@webdna.us <talk@webdna.us>
Sent: Wednesday, = February 19, 2020 09:32 AM
To: WebDNA Talk List = <talk@webdna.us>
Subject: Re: [WebDNA] COMMITDATABASE in = linux unix 64bits FastCGI version = 8.6

 

Hi = Terry

 

It is hard to work out who sent email to the =  list now that the =E2=80=9Cfrom" has = changed.

 

 

The call is very simple, a url with = variables. 

 

 

admin-switch.dna?task=3Dswitch-6&dbid=3D6&dbidn= ame=3DSM-ID&dbname=3Dshippingmethods&dbfield=3DSM-ACTIVE&acti= ve=3DT

 

 

The receiving page is very = simple too.



[REPLACE = db=3D../data/[DBNAME].db&eq[DBIDNAME]datarq=3D[DBID]&max=3D1][!]<= o:p>

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 [/!][DBFIELD]=3D[url][DBVALUE][/URL][!]<= /span>

[/!][/REPLACE]

 

 

The replace is 100% correct in the db file if I open = it up, the problem is that until I manually flush the dbs it is not = recognised.

 

I = have tried putting in [CLOSEDATABASE db=3D../data/[DBNAME].db] = or [COMMITDATABASE db=3D../data/[DBNAME].db] or even = [flushdatabases] with no resolution.

 

It is not the one db, I have another ajax update for = another db which has the same issue. I have not gone through the entire = system checking for others.

 

Kind = regards

 

Stuart = Tremain

Pharoah Lane = Software

AUSTRALIA

 

 

 

 

 



On 19 Feb 2020, at 12:11, talk@webdna.us = wrote:

 

Morning = Stuart,

 =

You = mentioned =E2=80=9CI have include [flushdatabases] in the ajax = call=E2=80=9D = =E2=80=A6.am I correct to say that you are either doing a GET or POST = Ajax call to a file sitting on the server that has the tags to execute = the flush webdna tag?

 =

If so = =E2=80=A6can share the ajax call script and the page called by it so = that I can try to assist you. It is indeed strange that the change is = stored in RAM but not committed into the DB even with all the settings = you mentioned. Regardless =E2=80=A6after the update, the uncommitted = change should still be showing up when called upon by other pages = relying on it.

 =

Cheers = TDn

 =

From:<= /b> = talk@webdna.us <talk@webdna.us> 
Sent: Wednesday, February 19, 2020 = 07:39 AM
To: WebDNA Talk List <talk@webdna.us>
Subject:<= span class=3Dapple-converted-space> 
[WebDNA] COMMITDATABASE = in linux unix 64bits FastCGI version = 8.6

 

I = am having an issue with a couple of = dbs.

 

Permissions are correct = 775

Ownership = is correct www-data:www-data

 

I am updating the db with an ajax call, I open the db = ofter it has been modified and the mod is there in the = db.

 

The ajax call does a replace on the = db.

 

There is no error reported from the ajax = call.




The WebDNA preference is "Automatically commit = databases to disk after = modification"

 

The problem is that another page on the site is = dependant on the new value. This new value is not being = found.

 

I have include [flushdatabases] in the ajax call to = force the db to clear however it is still not finding the new = value.

 

If I use the WebDNA admin to [flushdatabases] then the = page finds the new value.

 

Any ideas ?

 

Kind = regards

 

Stuart Tremain

Pharoah Lane = Software

AUSTRALIA

 

 

 

 

 

 

-------------------------------------------------------= -- 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://www.webdna.us/p= age.dna?numero=3D55 Bug Reporting: support@webdna.us

------------= --------------------------------------------- This message is sent to = you because you are subscribed to the mailing list talk@webdna.= us To = unsubscribe, E-mail to: talk-leave@w= ebdna.us archives: http://www.w= ebdna.us/page.dna?numero=3D55 Bug = Reporting: support@webd= na.us

 

-------------------------------------------------------= -- 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://www.webdna.us/p= age.dna?numero=3D55 Bug Reporting: support@webdna.us

--------------------------------------------------------- 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://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us ------=_NextPart_000_00FD_01D5E70F.0ABEF4B0-- . "Terry Nair"

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:

Date Sorting (1997) mass mailing (1998) bugs w/! &/or bad scripting??? (1997) Search with Special Chars (1997) Quit revisited (1997) Status? (2000) Protect (1997) all records returned. (1997) Grouping search fields, etc. (1997) Special characters in field names (1998) HELP WITH DATES (1997) Re[2]: Enhancement Request for WebCatalog-NT (1996) Signal Raised Error (1997) problems with 2 tags (1997) Email Mac (2002) Loosing Quantity (2000) oops private message leaked into talk list (1997) charging? (2001) Bad suffix error (1997) Help! (1999)