Potential Bug in Access 2003

MS Office Access

    Next

  • 1. Proper capitilization of names
    I want to use an update query to capitalize the first letter of each string and lower case the rest. The trick is there is a blank between strings within the field such as with proper names ie. John Doe Smith. I know I need to use the functions mid, lcase, and ucase in my update query, but am not quite getting it. Any help would be appreciated.
  • 2. Convert Dates
    You can use the DateSerial() function: NewField:DateSerial(Year([DateField]),Month([DateField]),1) Please reply only to this newsgroup. I do not reply to personal e-mail. "Mike" < XXXX@XXXXX.COM > wrote in message news:# XXXX@XXXXX.COM ... > I am using Access 2000 and have a field with over a 100,000 records that is > a Date Format - 7/31/2003. I would like to convert all dates such that the > Month and Year stay the same but the day of the month changes to "01." The > following are examples of what I would like: > > Records: > 7/31/2003 > 12/14/2002 > 4/2/2001 > > Converted to: > 7/01/2003 > 12/01/2002 > 4/01/2001 > > Any help would be greatly appreciated. > >
  • 3. Exporting select query to text
    Hi, I have a select query that runs off of a form. One parameter is selected in the form. The query runs fine. After I make the selection and run the query I would like to export it to a text or csv file. When I try to do this I get an error message that says "Too Few Parameters. Expected 1". I am not using any aliases in the query. I have tried to export with the form still open and after closing the form. Same result. Any help? I'm in Access 2000 on Windows 98. Thanks, Marc
  • 4. Find the most recent date for a record
    I have a table set up as follow: # Date1 Date2 Date3 Date 4 Date5 1 01/01/2000 12/20/2001 12/29/2001 03/15/2002 04/01/2003 2 12/15/2002 01/20/2003 01/25/2003 06/15/2003 3 09/05/1999 4 03/22/2001 04/25/2001 05/18/2002 5 08/07/2002 05/19/2003 06/15/2003 06/16/2003 07/31/2003 For each record, I need to know the most recent date. The result would be: # Result 1 04/01/2003 2 06/15/2003 3 09/05/1999 4 05/18/2003 5 07/31/2003

Potential Bug in Access 2003

Postby Simon Purdy » Wed, 03 Dec 2003 00:31:42 GMT

Hi

Interesting issue here.
Was working with the following SQL statement in Access 2003:-

SELECT     a.Text
FROM   (SELECT     NOTES.Text
                       FROM        PEOPLE INNER JOIN  NOTES ON
PEOPLE.Client_Id = NOTES.Client_Id AND PEOPLE.Contact_Number =
NOTES.Contact_Number) a
GROUP BY a.Text

NOTES.Text is a Memo field as it may store more than 255 Characters.

On running the query the Text field returns 2 unicode characters, it is my
belief that this is a 32 bit address for where the Note is stored. If the
Join is removed from the internal Select statement the returned Text field
is expected.

The above statement was cut down from a much longer statement in the form
it's used in.

Anybody else seen this and is there any solutions (I am unable to change the
structure of the SQL Statement unfortunately).

Many Thanks.

Si



Re: Potential Bug in Access 2003

Postby Douglas J. Steele » Wed, 03 Dec 2003 02:45:21 GMT

I don't believe it's possible to use Memo fields in GROUP BY statements.

I'd also suggest renaming the field to something other than Text: I suspect
that's a reserved word.

-- 
Doug Steele, Microsoft Access MVP
 http://www.**--****.com/ 
(No private e-mails, please)







the



Re: Potential Bug in Access 2003

Postby Gary Walter » Wed, 03 Dec 2003 07:39:40 GMT

"Simon Purdy" < XXXX@XXXXX.COM > wrote
Hi Si,

In addition to Douglas's sage advice,

1) would you mind verifying that Client_Id and Contact_Number
   fields are indexed in both tables?

2)would you mind trying

SELECT a.SortText, First(a.FullText) As FullMemo
FROM  (SELECT   Left(NOTES.[Text],255) As SortText,
                                NOTES.[Text] As FullText
               FROM  PEOPLE INNER JOIN  NOTES ON
              PEOPLE.Client_Id = NOTES.Client_Id
             AND PEOPLE.Contact_Number = NOTES.Contact_Number) a
GROUP BY a.SortText;

Thanks,

Gary Walter



Re: Potential Bug in Access 2003

Postby Gary Walter » Wed, 03 Dec 2003 07:45:45 GMT

"Simon Purdy" < XXXX@XXXXX.COM > wrote
Hi Si,

In addition to Douglas's sage advice,

1) would you mind verifying that Client_Id and Contact_Number
   fields are indexed in both tables?

2)would you mind trying

SELECT a.SortText, First(a.FullText) As FullMemo
FROM  (SELECT   Left(NOTES.[Text],255) As SortText,
                                NOTES.[Text] As FullText
               FROM  PEOPLE INNER JOIN  NOTES ON
              PEOPLE.Client_Id = NOTES.Client_Id
             AND PEOPLE.Contact_Number = NOTES.Contact_Number) a
GROUP BY a.SortText;

Thanks,

Gary Walter




Re: Potential Bug in Access 2003

Postby Simon Purdy » Wed, 03 Dec 2003 17:49:37 GMT

Thanks

You were correct about the not being able to group by memo fields.

The SQL code is autogenerated hence the rigid structure, I now have to
modify the code that generates the SQL.

Again, many thanks.

Si




suspect



my
the
field
form



Re: Potential Bug in Access 2003

Postby david epsom dot com dot au » Wed, 03 Dec 2003 18:19:37 GMT

Yes, last I checked (14 October 2003, SR7 "Access Bug,
Grouping by Memo")  there was still a bug when grouping
by Memo Fields.

Peter Miller described the bug last year, but it has
apparently existed since 'group by memo field' was
intoduced with Access 2000.

For Peter Miller's sample demonstration:
 http://www.**--****.com/ %404ax.com&rnum=5&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26q%3Dmemo%2Bbug%26btnG%3DGoogle%2BSearch%26meta%3Dgroup%253Dmicrosoft.public.access.*

or search for "BUG: Group by memo field in A2k or AXP"

In summary: only group by memo when using only ONE table,
or Use "Left" to select the first 255 characters of the
memo field, and group on that.

(david)






the



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



Return to MS Office Access

 

Who is online

Users browsing this forum: No registered users and 4 guest