Re: MS SQL (thats S not Y)
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 58858
interpreted = N
texte = As a public company, we cannot talk about future product plans ordevelopment roadmaps unless that information has been formally releasedto the investment community by way of a press release. =20Sharing detailed, unannounced information by answering your questionswould certainly violate insider trading policies. We cannot tell youwhat features will be in future versions. We cannot tell you whenfuture versions will be available. We cannot tell you what challengesthe development team is facing. We cannot tell you what a new productis going to cost. We cannot sell product that has not been released.There are other reasons we keep such information from public view untila press release; Decisions about products in development are madethroughout the development cycle in response to various factors. Until apress release is made available to the public announcing the launch of anew product, details such as feature set, market position, cost, etc.are known only to the development team members who "need to know."What I CAN tell you is that Smith Micro continues to study andunderstand market requirements and will always strive to developproducts that have the features and functionality the market expects.We recognize the importance of integration with MS SQL, and the workwith did with MySQL in 6.0 was specifically designed to build aframework where we could integrate other SQL-compliant databases fromother vendors.Sorry I cannot be more specific and I hope you understand.Doug-----Original Message-----From: Philip Edell [mailto:webmaster@kuhn-partner.com]=20Sent: Thursday, July 22, 2004 3:49 AMTo: WebDNA TalkCc: Doug DeckSubject: MS SQL (thats S not Y)Would it be possible to have an update concerning when the new SQL=20context will support Microsoft SQL server?In a thread titled: SQL Support in 6.0, Steve Contreras said we should=20expect support for MS SQL"relatively soon" (That was in mid February)Will this functionality be included in a forthcoming WebDNA 6.x version?Do I have to wait until 7.0 and upgrade?Have you developed this functionality and are waiting to release it?(if this is the case, please can I buy the upgrade now)Are you having trouble making it work?When do you estimate it will be available?Please can you share any information you can, as I have a client who=20needs to use this urgently.YoursPhilip Edell.-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list
.To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
As a public company, we cannot talk about future product plans ordevelopment roadmaps unless that information has been formally releasedto the investment community by way of a press release. =20Sharing detailed, unannounced information by answering your questionswould certainly violate insider trading policies. We cannot tell youwhat features will be in future versions. We cannot tell you whenfuture versions will be available. We cannot tell you what challengesthe development team is facing. We cannot tell you what a new productis going to cost. We cannot sell product that has not been released.There are other reasons we keep such information from public view untila press release; Decisions about products in development are madethroughout the development cycle in response to various factors. Until apress release is made available to the public announcing the launch of anew product, details such as feature set, market position, cost, etc.are known only to the development team members who "need to know."What I CAN tell you is that Smith Micro continues to study andunderstand market requirements and will always strive to developproducts that have the features and functionality the market expects.We recognize the importance of integration with MS SQL, and the workwith did with MySQL in 6.0 was specifically designed to build aframework where we could integrate other SQL-compliant databases fromother vendors.Sorry I cannot be more specific and I hope you understand.Doug-----Original Message-----From: Philip Edell [mailto:webmaster@kuhn-partner.com]=20Sent: Thursday, July 22, 2004 3:49 AMTo: WebDNA TalkCc: Doug DeckSubject: MS SQL (thats S not Y)Would it be possible to have an update concerning when the new SQL=20context will support Microsoft SQL server?In a thread titled: SQL Support in 6.0, Steve Contreras said we should=20expect support for MS SQL"relatively soon" (That was in mid February)Will this functionality be included in a forthcoming WebDNA 6.x version?Do I have to wait until 7.0 and upgrade?Have you developed this functionality and are waiting to release it?(if this is the case, please can I buy the upgrade now)Are you having trouble making it work?When do you estimate it will be available?Please can you share any information you can, as I have a client who=20needs to use this urgently.YoursPhilip Edell.-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
"Doug Deck"
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:
Guestbook (2000)
WebCat2b13MacPlugIn - [shownext method=post] ??? (1997)
File Uploads... (1997)
[date format] w/in sendmail (1997)
NT vs Mac (1997)
[WebDNA] Image Magick and Webdna (2009)
[WriteFile] problems (1997)
Size issues (2001)
Date Math broken on Mac OS X 10.4? (2007)
decrypt and summ problems (1999)
[shownext max=?] armed (1997)
ShowNext (1997)
[OT] WebDNA Family Album (2004)
Error.html (1997)
Secure Sever and showcart errors (1997)
verify online (1997)
Credit back woes (2000)
redirect from the errorsMessages.db entry (1997)
[searchString] (1997)
Trigger to empty shopping cart folder (2005)