Re: Selecting from a Combobox makes Access 2003 crash after SP3
- From: Spiky <Spiky@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 15 Oct 2007 02:23:01 -0700
The bit field and checkbox issue seems to be being caused by a differenec
between signed and unsigned values. Bits are unsigned and therefore not
boolean. Checkboxes are boolean and therefore signed. Changing the bit
field to a small int and the problem disappears. If you need to keep the bit
field then instead of a checkbox try a combo box with 'True' and 'False' in
it as values. Not nearly as nice but it does work.
"Sylvain Lafontaine" wrote:
By any chance, have you set any custom property on the fields A or B on the.
table; for example by setting a sorting order or a width for the column when
the table is opened/displayed in the database window?
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
wrote in message news:umMyxCt$HHA.5160@xxxxxxxxxxxxxxxxxxxxxxx
A good suggestion would be to rollback to SP2. Personally, I don't have
SP3 installed and it's no longer my intention to install it anymore.
Look like that with SP3, there is some kind of memory corruption problem
or something on the same line. By any change, are you making calls to
.RecordsetClone instead of RecordsetClone anywhere in your program? In
SP2, I've observed a lot of strange things happening after the use of
RecordsetClone.
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"Christian Andersson" <ChristianAndersson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:DD2F6021-01A1-47C3-85ED-B01047A97839@xxxxxxxxxxxxxxxx
Hi.
Thank you for your reply.
The rowsource is a simple Select.
And it works in many other, exactly the same, projects.
It's a "SELECT A,B from <Table> WHERE <integer DatatypeField> = 1"
2 columns, bound column = 1, column width = "0cm;10cm"
The Combobox is situated in a TabControl
We use the exakt same layout on the other 3 comboboxes on the other 3
tabs.
"SELECT A,B from <Table> WHERE <integer DatatypeField> = 2"
and then 3
and then 4.
All of these work fine.
The symptom does not occur on computers that do not have SP3 installed.
----------------------------
Another Problem:
We have discovered yet another problem after SP3.
We have 2 checkboxes, say "cb1" and "cb2"
And 2 textboxes, say "text1" and "text2"
On the event Click on cb1 the follwing code exists:
If Me.cb1.Value = True Then
Me.text1.Value = Date
Else
Me.text1.Value = Null
End If
and the same code for cb2 updating text2.
For some reason the state (true/false) of the checkbox is no longer
updated.
Access just enters the Click_event without first doing what the inherent
function of a checkbox is, to toggle between True and False.
The symptom does not occur on computers that do not have SP3 installed.
--------------------------
The same thing about the bit CustomerLocked problem.
The symptom does not occur on computers that do not have SP3 installed.
All of these symptoms started last Thursday, when SP3 was installed.
So something in SP3 confuses Access majorly!
"Sylvain Lafontaine" wrote:
Try changing the RowSource of the ComboBox to something else similar.
For
example, if it's the name of a SP, then try replacing with an EXEC
statement
that it's changed every time the parameters are changed (for example, on
the
OnCurrent event of the form).
Any particular field in the query, for example a bit field or a decimal
value?
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"Christian Andersson" <ChristianAndersson@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote
in message news:B58618A1-89DE-483A-ABF5-7A5933C20277@xxxxxxxxxxxxxxxx
After SP3 for Office 2003 was installed last Thursday we have had some
problems.
One of the problems are that Access2003 crashes when we try to select
a
value from a ComboBox.
We use many different ADP files, each connected to a database on our
SQL
2k
server.
On a few of these projects, we are unable to select values from a
certain
combobox.
The form opens up ok, all the boxes are filled with the correct
values.
One of the boxes, say "cbxReply", has 2 values. An event (change) is
connected to that through VBA code.
If we try to select a value from that box, Access crashes. Íf I set a
breakpoint on the change event, I can see that Access crashes before I
even
get to there.
But, if I add some code to the event "Before Update", then the code
runs
as
normal and it seems to work just fine.
But the exakt same code seems to work fine on our other running
projects.
Im at a loss here as to what the cause may be... ?
For some reason, on this case, Access must lose its way while trying
to
figure out what event to handle, and then crashes...
Suggestions?
- Follow-Ups:
- Re: Selecting from a Combobox makes Access 2003 crash after SP3
- From: Sylvain Lafontaine
- Re: Selecting from a Combobox makes Access 2003 crash after SP3
- Prev by Date: Re: Selecting from a Combobox makes Access 2003 crash after SP3
- Next by Date: Re: Insert Error 30014
- Previous by thread: Re: Selecting from a Combobox makes Access 2003 crash after SP3
- Next by thread: Re: Selecting from a Combobox makes Access 2003 crash after SP3
- Index(es):
Relevant Pages
|
