....my patience wears thin with your toddler temper tantrums ...with the
number of caustic posts you've made lately ...most of absolutely zero value
to the question asked ...I wonder when you find time to remove your head
from your ass long enough to create these works of wonder you so rapturously
describe ...most likely in your dreams, eh.
....lest you not be paying great attention, Microsoft has made it abundantly
clear that its front end development platform of choice for SQL Server is
not Access but a dotNet language ...the Jet database engine that drives
Access has been removed from the SQL Server development team and handed to
the Access development team for all future development ...read this comment
from the Access Development Team itself ...and then perhaps we can count on
you to shut up:
"The two weaknesses of ADPs that likely won’t be fixed because of the
underlying architecture include the inability to link to external data
sources (without setting up linked servers) and local queries. Combining
adhoc heterogeneous data sources is a big part of Access functionality that
is used heavily by most customers. The Access team is making a big
investment in using the Access Data Engine as the way to get to external
data sources. I expect that to continue in the future.
For new SQL Server projects where you are evaluating which platform to start
from, we recommend MDBs or ACCDBs with linked tables because they offer more
flexibility and that is likely where the Access team will invest the most
when building new features.
We have also found that applications that are upsized from mdb back-end
tables to SQL Server link tables require far less application changes than
upsizing to ADPs. The upsizing wizard defaults have been changed from
upsizing to ADPs to move the data to SQL Server and replace local tables
with link tables. In other words, the upsizing wizard will not default to
ADPs."
http://blogs.msdn.com/access/comments/602128.aspx
....so tell us oh great ADP wizard, who's working with a "DED" database
format now, eh?
William Hindman