Access 2003 vs Access 2007

**lyle fairfield** · Aug 21 '08, 02:35 AM

Re: Access 2003 vs Access 2007

Microsoft spent big bucks developing and streamlining the Access/
Windows GUI, including scrollbars and default navigation buttons. They
are fast, slick, and, TTBOMK, foolproof. Use them!
Forms are for editing data, not silly buttons.

On Aug 20, 10:12 pm, pballou <pbal...@nctc.c omwrote:

> Any Suggestions?

**pballou** · Aug 21 '08, 02:45 AM

Re: Access 2003 vs Access 2007

On Aug 20, 9:28 pm, lyle fairfield <lyle.fairfi... @gmail.comwrote :

Microsoft spent big bucks developing and streamlining the Access/
Windows GUI, including scrollbars and default navigation buttons. They
are fast, slick, and, TTBOMK, foolproof. Use them!
Forms are for editing data, not silly buttons.
>
On Aug 20, 10:12 pm, pballou <pbal...@nctc.c omwrote:
>
>
>

Any Suggestions?- Hide quoted text -

>
- Show quoted text -

I just simplified the code to make it easy to understand the problem.
I am doing alot more than just trying to move down the page. It is
part of scheduling program that moves through dates and times to find
open time slots. With that being said do you have any ideas why the
values from the form are not changing??

**Albert D. Kallal** · Aug 21 '08, 02:55 AM

Re: Access 2003 vs Access 2007

I don't see why the code would not work in 07.

I would do a few things:

first, do a debug->compile while looking at the code. Does it compile?

And, you could try:

try using me.formField1 in place of [formField]. Or even me!FormField1

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKa llal@msn.com

**Albert D. Kallal** · Aug 21 '08, 02:55 AM

Re: Access 2003 vs Access 2007

I don't see why the code would not work in 07.

I would do a few things:

first, do a debug->compile while looking at the code. Does it compile?

And, you could try:

try using me.formField1 in place of [formField]. Or even me!FormField1

And, if it has spaces, then perhaps try:

me![FormField]

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKa llal@msn.com

**Salad** · Aug 21 '08, 03:25 AM

Re: Access 2003 vs Access 2007

pballou wrote:

The is a simple example of code that worked in access 2003 but does
not in access 2007. I have checked it with the debugger and the
reason is the value of formField1 does not change in ver. 2007 in the
code as the docmd.gotorecor d,,acnext moves down the records. But it
does in ver 2003. Any Suggestions?
>
Example of Table displayed in a continous form with 5 records.
1
1
1
2
3
>
Example Code:
>
When double Clicking on the 1st record the cursor should move to
record 4.
>
Private Sub formField1_DblC lick(Cancel As Integer)
dim vTest as Byte
>
vTest = 1
>
Do While [formField1] = vTest
DoCmd.GoToRecor d , , acNext
Loop
>
End Sub
>
Thanks.

Why is vTest set to 1? Why not set vTest to the value of formField1? Ex:

dim vTest as Variant 'have no idea what formField1 is

vTest = Me![formField1]

Do While Me![formField1] = vTest
DoCmd.GoToRecor d , , acNext
Loop

BTW, are you updating formField1 as you loop thru the code? Your
description of your problem, what is occurring, what should occur could
use some fleshing out. Why should the value change? Until you provide
a better detailing I believe you'll get some stabs and guesses at what
you are attempting to do as a fix, not a real solution.

**pballou** · Aug 21 '08, 03:35 AM

Re: Access 2003 vs Access 2007

On Aug 20, 9:49 pm, "Albert D. Kallal" <PleaseNOOOsPAM mkal...@msn.com >
wrote:

I don't see why the code would not work in 07.
>
I would do a few things:
>
first, do a debug->compile while looking at the code. Does it compile?
>
And, you could try:
>
try using me.formField1 in place of [formField]. Or even me!FormField1
>
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKa l...@msn.com

Thanks for your suggestions.

Sorry I replied to Author instead of reply.

I don't submit very many questions to the groups.
Normally I can find my answers just by reading other people's
questions.

This one has stumped me.

It will compile and I tried the me. and me! reference. Still no
luck.
I've been trying everything for a couple of days.

This has been working fine at about 7 customers for several years.
One of my customers had their computers stolen and upgraded to 2007
and I tested the program and found this problem. In my scheduling
program the docmd.gotorecor d,,acnext moves down and back up the form
to record the dates and times already scheduled.

Any other ways to move up and down a form other than
"Docmd.GotoReco rd,,acNext"?
I've already tried sendkeys with the down arrow and the tab key. It
will move but it will still no change in the value.

I've put in a msgbox after each move statement to see if it is moving
and it does but no value changed. It's like it gets the first
record's value but never updates as it moves.

Any suggestions would be greatly appreciated.

Thanks

**Albert D. Kallal** · Aug 21 '08, 05:05 AM

Re: Access 2003 vs Access 2007

You certainly can writet he code differt. I would perahps change the vTest
as byte to

dim vTest as Varient and see if that works.

I assume that other code in the application runs fine??

I am perplexed why your code don't work. There nothing inhenerent in 2007
that changed that should cause a problem.

You could rewrite the code as:

Dim rst As DAO.Recordset
Dim vTest As Variant

vTest = 1
Set rst = Me.Recordset
Do While rst!FormField1 = vTest
rst.MoveNext
Loop

Note that you need to replace "formField1 " with the actual name of the
underlying field in the table, NOT the actual name of the contorl used on
the form (often they are the SAME name, but often they are not).

Does most other code run just fine in the application?

Try the above..it should work

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKa llal@msn.com

**Salad** · Aug 21 '08, 05:25 AM

Re: Access 2003 vs Access 2007

pballou wrote:

On Aug 20, 9:49 pm, "Albert D. Kallal" <PleaseNOOOsPAM mkal...@msn.com >
wrote:
>

>>I don't see why the code would not work in 07.
>>
>>I would do a few things:
>>
>>first, do a debug->compile while looking at the code. Does it compile?
>>
>>And, you could try:
>>
> try using me.formField1 in place of [formField]. Or even me!FormField1
>>
>>--
>>Albert D. Kallal (Access MVP)
>>Edmonton, Alberta Canada
>>pleaseNOOSpam Kal...@msn.com

>
>
Thanks for your suggestions.
>
Sorry I replied to Author instead of reply.
>
I don't submit very many questions to the groups.
Normally I can find my answers just by reading other people's
questions.
>
This one has stumped me.
>
It will compile and I tried the me. and me! reference. Still no
luck.
I've been trying everything for a couple of days.
>
This has been working fine at about 7 customers for several years.
One of my customers had their computers stolen and upgraded to 2007
and I tested the program and found this problem. In my scheduling
program the docmd.gotorecor d,,acnext moves down and back up the form
to record the dates and times already scheduled.
>
Any other ways to move up and down a form other than
"Docmd.GotoReco rd,,acNext"?

Dim rst = Me.Recordsetclo ne
rst.bookmark = me.bookmark
Do while not rst.eof
rst.movenext
If field <var then exit do
Loop
if rst.eof then rst.movepreviou s
me.bookmark = rst.bookmark

I've already tried sendkeys with the down arrow and the tab key. It
will move but it will still no change in the value.

I've put in a msgbox after each move statement to see if it is moving
and it does but no value changed. It's like it gets the first
record's value but never updates as it moves.
>
Any suggestions would be greatly appreciated.

Yeah. Tell us what you want to do. What's all this about "change in
the value" stuff mean.

>
Thanks

**lyle fairfield** · Aug 21 '08, 09:45 PM

Re: Access 2003 vs Access 2007

Checking this it !!!SEEMS!!! that Access 2007 code does !!!NOT!!!
return the value of a textbox in the record to which we have moved
with DoCmd.GoToRecor d from !!!WITHIN!!! the procedure where the
DoCmd.GoToRecor d lives (after the DoCmd.GoToRecor d is called). It
continues with the original value of the text box in the record before
DoCmd.GoToRecor d is called. This is as the OP reported.

I was successful in retrieving this value only in the form's OnCurrent
event code as follows:
(Northwinds 2007 - Form:Purchase_O rder_List

Dim SupplierID&

Private Sub Form_Current()
SupplierID = Supplier_ID.Val ue
End Sub

Private Sub Purchase_Order_ ID_Click()
Dim TestSupplierID&
TestSupplierID = Supplier_ID.Val ue
Do
DoCmd.GoToRecor d
If SupplierID <TestSupplier ID Then Exit Do
Loop
End Sub

(What does this do? It moves down the continuous form while the
supplier is the same supplier as in the record where we started).

Have I tested this notion thoroughly? Nope!
Is the behaviour different than in earlier versions of Access? TTBOMR,
yes, but I didn't test that.
Could the OP solve his problem with my code modified? Maybe; my guess
is "Yes".
Could my code be streamlined. Sure. Go ahead!

On Aug 20, 10:41 pm, pballou <pbal...@nctc.c omwrote:

On Aug 20, 9:28 pm, lyle fairfield <lyle.fairfi... @gmail.comwrote :
>

Microsoft spent big bucks developing and streamlining the Access/
Windows GUI, including scrollbars and default navigation buttons. They
are fast, slick, and, TTBOMK, foolproof. Use them!
Forms are for editing data, not silly buttons.

>

On Aug 20, 10:12 pm, pballou <pbal...@nctc.c omwrote:

>

> Any Suggestions?- Hide quoted text -

>

- Show quoted text -

>
I just simplified the code to make it easy to understand the problem.
I am doing alot more than just trying to move down the page. It is
part of scheduling program that moves through dates and times to find
open time slots. With that being said do you have any ideas why the
values from the form are not changing??

**pballou** · Aug 22 '08, 02:15 AM

Re: Access 2003 vs Access 2007

On Aug 21, 4:35 pm, lyle fairfield <lyle.fairfi... @gmail.comwrote :

Checking this it !!!SEEMS!!! that Access 2007 code does !!!NOT!!!
return the value of a textbox in the record to which we have moved
with DoCmd.GoToRecor d from !!!WITHIN!!! the procedure where the
DoCmd.GoToRecor d lives (after the DoCmd.GoToRecor d is called). It
continues with the original value of the text box in the record before
DoCmd.GoToRecor d is called. This is as the OP reported.
>
I was successful in retrieving this value only in the form's OnCurrent
event code as follows:
(Northwinds 2007 - Form:Purchase_O rder_List
>
Dim SupplierID&
>
Private Sub Form_Current()
SupplierID = Supplier_ID.Val ue
End Sub
>
Private Sub Purchase_Order_ ID_Click()
Dim TestSupplierID&
TestSupplierID = Supplier_ID.Val ue
Do
DoCmd.GoToRecor d
If SupplierID <TestSupplier ID Then Exit Do
Loop
End Sub
>
(What does this do? It moves down the continuous form while the
supplier is the same supplier as in the record where we started).
>
Have I tested this notion thoroughly? Nope!
Is the behaviour different than in earlier versions of Access? TTBOMR,
yes, but I didn't test that.
Could the OP solve his problem with my code modified? Maybe; my guess
is "Yes".
Could my code be streamlined. Sure. Go ahead!
>
On Aug 20, 10:41 pm, pballou <pbal...@nctc.c omwrote:
>
>
>

On Aug 20, 9:28 pm, lyle fairfield <lyle.fairfi... @gmail.comwrote :

>

Microsoft spent big bucks developing and streamlining the Access/
Windows GUI, including scrollbars and default navigation buttons. They
are fast, slick, and, TTBOMK, foolproof. Use them!
Forms are for editing data, not silly buttons.

>

On Aug 20, 10:12 pm, pballou <pbal...@nctc.c omwrote:

>

Any Suggestions?- Hide quoted text -

>

- Show quoted text -

>

I just simplified the code to make it easy to understand the problem.
I am doing alot more than just trying to move down the page. It is
part of scheduling program that moves through dates and times to find
open time slots. With that being said do you have any ideas why the
values from the form are not changing??- Hide quoted text -

>
- Show quoted text -

Lyle, You are the MAN!

This is exactly what I needed and I would never have found it.

Thanks.

**David W. Fenton** · Aug 22 '08, 04:45 AM

Re: Access 2003 vs Access 2007

Salad <oil@vinegar.co mwrote in
news:4YqdnTX9ec ApZjHVnZ2dnUVZ_ sbinZ2d@earthli nk.com:

Dim rst = Me.Recordsetclo ne
rst.bookmark = me.bookmark
Do while not rst.eof
rst.movenext
If field <var then exit do
Loop
if rst.eof then rst.movepreviou s
me.bookmark = rst.bookmark

Please don't recommend that people write code like that. Instead:

With Me.RecordsetClo ne
.Bookmark = Me.Bookmark
Do While Not .EOF
.Movenext
If field <var then exit do
Loop
If .EOF then .MovePrevious
Me.Bookmark = .Bookmark
End With

But if you *do* recommend unnecessarily initializing a recordset
variable, be sure that you clean up by ending your code with:

Set rst = Nothing

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

**David W. Fenton** · Aug 22 '08, 04:45 AM

Re: Access 2003 vs Access 2007

pballou <pballou@nctc.c omwrote in
news:67860eaa-0ade-46dd-af60-0a70da9e45fd@f6 3g2000hsf.googl egroups.co
m:

I am doing alot more than just trying to move down the page. It
is part of scheduling program that moves through dates and times
to find open time slots.

It is likely that you should be able to get the answer with SQL
instead of jumping around in a form's recordset (or RecordsetClone) .

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Access 2003 vs Access 2007

Access 2003 vs Access 2007

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment