Code does not work in 64 Bit Access 2010

[mwolfod]

When you single step, does the code get to the API call?

Sorry, I don't know what you mean by "API call".

On DEBUG single step it "jumps" out of the code to the accompanying module, where it demands that ptrSafe be inserted in the Declare statements, then as mentioned, after compiling, the code ceases to function (that is, no response when the Command Button the code is attached to is clicked).

[RuralGuy]

This is the line in the code that actually makes the API call. I take it single stepping never gets there after puting in the ptrSafe, whatever that is. Do you have a link that describes what to do with ptrSafe? I'll google it for now.

   Me.ODPosteriorSegmentImagePath1TextBox = ahtCommonFileOpenSave(InitialDir:=strStartDir, _
                                                                  Filter:=strFilter, FilterIndex:=3, Flags:=lngFlags, _
                                                                  DialogTitle:="Select File")

[RuralGuy]

Here's a good article about the changes needed when using the 64bit VBA code. http://msdn.microsoft.com/en-us/library/ee691831.aspx

[mwolfod]

Ok, when I now F8 from the previous line to the line you specify, the DEBUG jumps to a Function (see attached Capture).

[mwolfod]

Here's a good article about the changes needed when using the 64bit VBA code. http://msdn.microsoft.com/en-us/library/ee691831.aspx

I think I am going to stick with 32 bit. I really wanted to make a full move to 64 bit ALL AT ONCE, but it seems I'm WAY ahead of the game.

At this time, the advantages of 64 bit seem rather arcane and limited.

Besides when this stuff is new to even the pros, I know I'm out in deeper water than I should be.

[RuralGuy]

Can you keep pressing F8 and get it to advance a line at a time?

[mwolfod]

Can you keep pressing F8 and get it to advance a line at a time?

Yes.

It steps through the lines of the Function I pasted, then, when completely through that, back up to the original code block, then "jumps" out again to another Function, which can be stepped though line-by line without error, then back again to the original code, at which point I can F8 through to the end.

[RuralGuy]

I think I am going to stick with 32 bit. I really wanted to make a full move to 64 bit ALL AT ONCE, but it seems I'm WAY ahead of the game.

At this time, the advantages of 64 bit seem rather arcane and limited.

Besides when this stuff is new to even the pros, I know I'm out in deeper water than I should be.

That is *your* choice of course and at this time there is no advantage to running true 64bit, plus the 32bit code will run on a 64bit machine.

[RuralGuy]

You need to make sure your pointers are on 64bit boundries which is why ptrSafe has the new data types.

[mwolfod]

That is *your* choice of course and at this time there is no advantage to running true 64bit, plus the 32bit code will run on a 64bit machine.

Right.

Thanks very much for your help. I do appreciate it.

I undoubtedly will have some rough spots converting from 2003 to 32 bit 2010, and am counting heavily on getting help from the good folks here.

[RuralGuy]

MVP Allen Browne may have some notes you will find useful. http://allenbrowne.com/Access2007.html

[mwolfod]

Thank you.