Similar Threads:
1.Potential Bug in Access 2007
I have noticed behavior in Access 2007 that could potentially delete/remove
relationships in your database when you try to split the database into a
front end and a back end using the 鈥淒atabase Tools鈥?>鈥滱ccess Database鈥?
option. If you have a table locked (such as having the table open or a form
(such as the switchboard) accessing a table) when you try and split the
database you will get the following error 鈥淭he database engine could not lock
table 鈥榯able_name鈥?because it is already in use by another person or
process.鈥? After clicking okay you will notice the split did not succeed
because you still have all of your local tables and no linked tables. You
will also notice all of your relationships defined in the database have been
deleted. Now the back end is created correctly. The tables exist and the
relationships are still defined. Now if you don鈥檛 realize your relationships
have been deleted you might delete the back end (since it does not contain
any of your custom objects, form, reports and so on) and try to redo the
split after releasing the lock on your table. The problem is the split works
but the back end is created without any relationships.
I just thought I would share this in hopes that somebody could avoid losing
their relationships. Always backup you database before doing a split.
2.Potential conflicts between Access 2003 runtime & Access 97/2000/X
I once installed Access 2000 runtime on a computer that had the full version
of Access 97, and when I uninstalled the runtime, Access 97 would no longer
run and had to be reinstalled.
Is there any possibility of my Access 2003 runtime distribution causing such
problems with a user's full version of Access 97/2000/XP? If this could
happen, I need to provide a disclaimer or warning when I distribute the 2003
runtime along with my applications.
3.Access 2003 - potential missing VBA references
Hello,
I use access 2003 developer extensions to package my access aplication and
one of its utilities (custom startup wizard) showed me a "potential missing
VBA references" which is Microsoft Scripting Runtime
(C:\windows\system32\scrrun.dll), a library I used to extract physical serial
number of a HDD on the target PC. I red also articles about references, but
I'm still a bit confused.
How can I manage this?
--
gabi braharu
4.Access 2003 - Access 2002 short time bug
Hi all,
I developed a web site for an institute. The site's database is based
on Access.
The database was placed on the Web Server (not my decision...) in a
shared folder which can be accessed from computers in the institute's
network only.
Another programmer has developed a UI with Access 2002. This UI
enables people from the institute to enter data to the database which
is later used by the site I developed. On the web server we got Office
2003 installed.
The problem is this:
When time is entered through the UI (using Access 2002) with a short
time format (i.e. hh:mm) it somehow changes its format in the Access
2003 environment to hh:mm:ss. If the table with the time field is
opened with Access 2002 one sees the format requested. However, if the
same table is opened using Access 2003, some of the records have the
format hh:mm:ss.
We cannot explain / fix this bug.
It should be noted that a format such as hh:mm:ss does not exist by
its own.
The next possible time format is medium format and it should include
the a.m. / p.m. (i.e. hh:mm:ss A.M.)
As far as the UI is concerned the time can only be entered in s
certain way (i.e. hh:mm). It doesn't allow the user to enter a
different format.
Has anyone encoutered this bug? Your help will be most appreciated.
Thanks,
5.BUG in conversion of Access 97 to access 2003
When data is converted from an access 97 database to Access 2000 format using
Access 2003 application, additional replication fields are added to each
table. However, unlike in Access 97 these extra fields are incorporated into
the visible structure of the converted table. The added fields displace
designed data fields in queries that user positional information for the
retrieval of data, i.e a combo box or list box.
At the very lease, if Access 2003 is going to modify the schema of a table
it should make the modification at the end of the table rather than at the
beginning.
6. Bug fixed in Access 2003 re-introduced in Access 2007
7. Access 2003 - Access 2002 short time bug
8. Potential conflict between Office 2000 and Office 2003 Group Policies