Code works when stepping but not when running (1 Viewer)

C

cheer

Registered User.

Local time

Today, 17:03

Joined

Oct 30, 2009

Messages

222

• Aug 17, 2017

• #1

It work perfectly when in MDB when execute from main screen till the screen you are looking for.

However, after migrating to Access 2017 (64 bits) and Windows 2012 Server (64 bits), a lot of problem errors seem like appear. Anyone know why it behave abnormally at the highlighted code in red colour ?

Set cnn = New adodb.Connection
cnnNew.ConnectionString = const_MDB
cnnNew.CommandTimeout = const_ConnectionTimeOut
cnnNew.CursorLocation = adUseClient
If cnnNew.State = adStateClosed Then cnnNew.Open

 

Minty

AWF VIP

Local time

Today, 10:03

Joined

Jul 26, 2013

Messages

10,368

• Aug 17, 2017

• #2

Am MDB is by nature 32 bit, and I'm sure you can't convert from mdb to access 2017 directly, you need to convert from 2003 (mdb) to 2007/10 format , then to 2016 onward.

Also there are difference in 32 bit and 64 bit access, have a search on here e.g. https://access-programmers.co.uk/forums/showthread.php?t=243843

 

C

cheer

Registered User.

Local time

Today, 17:03

Joined

Oct 30, 2009

Messages

222

• Aug 17, 2017

• #3

I have imported all forms into accdb environment.

Only 10% of forms can't work. However, those forms work perfectly if through debugging. I don't understand why it behave like this?

 

Minty

AWF VIP

Local time

Today, 10:03

Joined

Jul 26, 2013

Messages

10,368

• Aug 17, 2017

• #4

The "correctness" factor in VBA code has been tightened up over version updates, so it's possible that something that was working in <=2003 versions may not now be completely correct as far as 2017 VBA is concerned.

If you compile the VBA does it highlight any errors?

 

missinglinq

AWF VIP

Local time

Today, 05:03

Joined

Jun 20, 2003

Messages

6,423

• Aug 17, 2017

• #5

cheer said:

...those forms work perfectly if through debugging. I don't understand why it behave like this...

Click to expand...

As a rule, when something works when stepping through the code, but doesn't work when being executed normally, there is a timing problem in the code. What, exactly, is being done in the Forms that are the problem?

Linq ;0)>

 

S

static

Registered User.

Local time

Today, 10:03

Joined

Nov 2, 2015

Messages

823

• Aug 17, 2017

• #6

If you've upgraded the back-end, you need a different connection string for accdb than you used for mdb.

https://www.connectionstrings.com/access/

Why are you using ADO instead of DAO anyway?

 

arnelgp

..forever waiting... waiting for jellybean!

Local time

Today, 17:03

Joined

May 7, 2009

Messages

19,232

• Aug 17, 2017

• #7

I think in connection string. New access uses ace ole and not jet 4.