If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Server2003 too Server2008
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 |
#2
|
|||
|
|||
Server2003 too Server2008
if your database corrupts, I'd reccomend moving to SQL Server- the
worlds most popular database 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 |
#3
|
|||
|
|||
Server2003 too Server2008
On Wed, 2 Jun 2010 17:55:49 +0100, "Peter Kinsman"
wrote: 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. This is a symptom of bad or missing references. From the VBA code editor, choose Debug..References. Correct any missing references. It's likely that you have some references to components that were on your old server but not on your new one. If you have references to other Office applications (like Word, Excel, etc.) you may want to consider using late binding instead of early binding. There are many articles on that subject. Armen Stein Microsoft Access MVP www.JStreetTech.com |
#4
|
|||
|
|||
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 |
#5
|
|||
|
|||
Server2003 too Server2008
I assume that you mean Tools/References to check for missing links, but in
most cases none come up as missing. When trying to delete a redundant form, I am getting a "Can't find project or library" message, which reinforces your suggestion. Many thanks Peter "Armen Stein" wrote in message ... On Wed, 2 Jun 2010 17:55:49 +0100, "Peter Kinsman" wrote: 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. This is a symptom of bad or missing references. From the VBA code editor, choose Debug..References. Correct any missing references. It's likely that you have some references to components that were on your old server but not on your new one. If you have references to other Office applications (like Word, Excel, etc.) you may want to consider using late binding instead of early binding. There are many articles on that subject. Armen Stein Microsoft Access MVP www.JStreetTech.com |
Thread Tools | |
Display Modes | |
|
|