View Single Post
  #4  
Old June 3rd, 2010, 02:21 AM posted to microsoft.public.access
Access Developer
external usenet poster
 
Posts: 12
Default Server2003 too Server2008

"a a r o n _ k e m p f" wrote

if your database corrupts, I'd reccomend moving to
SQL Server- the worlds most popular database.


Mr. Kempf, do you not even read the posts before handing out your usual
advice?

The poster clearly stated that he is *already* using SQL Server, and
converting from the 2003 version to the 2008 version. Do you have advice
regarding the conversion he asked about?

I believe you need to change your description from "the worlds most popular
database" to "the world's most popular commercial server database" if you
care about being truthful. There are uncounted thousands, perhaps millions,
of Jet and ACE databases in use if you do not qualify with "server"
database, and there are uncounted thousands of Open Source server databases,
such as MySQL, if you do not qualify with "commercial".

Larry Linson, Microsoft Office Access MVP
Co-author of "Microsoft Access Small Business Solutions" pub by Wiley
Access newsgroup support is alive and well at comp.databases.ms-access in
USENET



On Jun 2, 9:55 am, "Peter Kinsman" wrote:
I create the databases but don't look after the hardware.

A client using Terminal Server is in the process of upgrading from
Server2003 and SBS2003 to the 2008 equivalents. A number of built-in
functions such as Format and Date are causing problems.
As an example, I created a new database with a form displaying Now()
Date()
and Format(Date(), "dd/mm/yy"). When in its own database, the form
displayed correctly, but when exported to an existing database it didn't,
which makes me think that something about the structure of an empty
database
has become corrupted.
Any suggestion please?

Many thanks

Peter Kinsman