Having a problem with Geopak GetJobNumbersWithinAcdtiveDir

I have one VBA that will not find the gpk file. Using the same code that works on the other VBA. Below is the code from the example which is used to check. The result returns the path/jobjob104.gpk

Dim jobNums()   As String
    Dim count       As Integer
    Dim myCogo      As Cogo

'Array of Job Numbers
jobNums() = GetJobNumbersWithinActiveDir()

    For count = LBound(jobNums) To UBound(jobNums)
        'Get the first Job Number in the array
        If 0 = count Then
            'Set the active Job Number
            Set myCogo = OpenCogoByJobNumber(104)
            'Set myCogo = OpenCogoByJobNumber(jobNums(count))

            If (myCogo Is Nothing) Then
                MsgBox "error reading job: " & jobNums(count)
            Else
                MsgBox myCogo.FullFileName
            End If

End If

Next count

Parents

0 Offline Artur Goldsweer Mon, Jul 27 2015 7:59 AM
Hi Larry,

Do you receive any error message? Or which indicator do you have the .gpk file is not found?

Two points are crossing my mind:
- this example is assuming the lower boundary of the array jobNums is 0.
In case the Compiler Option Base 1 is used, the lower boundary will be 1 and the desired job not found.
Can you please check in your source code, if you can find a line with:
Option Base 1

- Did you check if the .gpk file is located in the right folder. To be sure please compare the file location with the content of the configuration variable _dgndir

Best regards,
Artur
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Mozart319 Mon, Jul 27 2015 8:12 AM in reply to Artur Goldsweer

Artur,
The code I'm using is directly from the help file and it is working with other VBAs. For some reason in this VBA it is reading it as \path\\jobjob104.

Larry

Larry Wilson
LWilson@LJBinc.com
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Robert Hook Mon, Jul 27 2015 12:25 PM in reply to Mozart319
Hi Larry,

Per the testing performed so far..

Would you mind running the test code above with the .dgn and .gpk files copied to a local test directory and report on those results?

If the code fails locally could you provide a test case to troubleshoot further?

If the code only fails when the data is located on the network drive consider capturing a Microsoft Process Monitor (procmon) log including "All Events" that cover the start of Geopak, opening the design and gpk files used, and the running of your code to the point of an error/unexpected result, then stop the procmon logging. Save the log as a .pml file then zip and attach the log file for review.

Thank you,
Bob
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Mozart319 Mon, Jul 27 2015 12:54 PM in reply to Robert Hook

Bob,

Move dgn and gpk locally and then made a project to read it locally. Still same problem
Here are the results of the 2 previous test that was run on the network.

GPK_JOBDIR: NOT DEFINED
GPK_CWD: C:\WorkFolder
_DGNFILE: C:\WorkFolder\88223RB001.dgn
Cogo.FullFileName: C:\WorkFolder\jobjob104.gpk

Jobnumber: 0, 104

Larry Wilson
LWilson@LJBinc.com
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Nico Roman Tue, Jul 28 2015 8:40 AM in reply to Mozart319
do you mean Cogo.FullFileName: C:\WorkFolder\job104.gpk ?

For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel
0 Offline Mozart319 Tue, Jul 28 2015 8:45 AM in reply to Nico Roman

Nico,

Cogo.FullFileName: C:\WorkFolder\jobjob104.gpk is what is being returned. What I don't understand is that I'm using the exact same code on other vbas and they are working fine. I have had this one around for years and all of sudden it has problems finding the gpk file.

Larry Wilson
LWilson@LJBinc.com
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Nico Roman Tue, Jul 28 2015 8:57 AM in reply to Mozart319
ok. it was just a guess, I would also try to simplify the folder names containing the gpk. try a path without special characters something simple like c:\temp

For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki
Answer Verified By: Mozart319
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Reply

0 Offline Nico Roman Tue, Jul 28 2015 8:57 AM in reply to Mozart319
ok. it was just a guess, I would also try to simplify the folder names containing the gpk. try a path without special characters something simple like c:\temp

For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki
Answer Verified By: Mozart319
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Children

0 Offline Mozart319 Tue, Jul 28 2015 9:00 AM in reply to Nico Roman

I tried C:\WorkFolder, see above.

Larry Wilson
LWilson@LJBinc.com
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Robert Hook Tue, Jul 28 2015 11:27 PM in reply to Mozart319
Prior to requiring computer specific logging to be performed, I would recommend these actions:

Import your MicroStation VBA project source code files into a new project. Doing so will ensure there is no underlying Microsoft VBA project corruptions. Right click on each module, class, and form exporting each as a separate source code file that can be imported into a new/clean MicroStation VBA project container.

Trap errors and Compile the MicroStation VBA Project. The default Microsoft VBA programming environment options are tuned more towards providing less user feedback/interruptions and have the unfortunate side-effect of masking/hiding errors that programmers should be aware of. In your Microsoft VBA development environment (not for production users) start by using the following Microsoft VBA project settings, then compile your VBA project:

Tools > Options > Editor Tab > Code Settings, Check: "Require Variable Declaration"

Tools > Options > General Tab > Error Trapping, Check: "Break on Unhandled Errors"

Tools > Options > General Tab > Compile:

Check: "Compile On Demand"

Check: "Background Compile"

Debug > Compile <your project name>

Provide a small concise test case (minimal data and code) required for others willing to help to be able to reproduce the exact issue being experienced. This will result in vastly improved times to resolution of issues being encountered and is analogous to a picture being worth a thousand words.

Change or perform only one item at a time and report back exact results experienced.
REFERENCE: David Agans - http://debuggingrules.com/ (DebuggingRules.jpg)

HTH,
Bob
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Mozart319 Fri, Aug 7 2015 10:27 AM in reply to Robert Hook

Bob,
Sorry it took so long to back to you, the work and deadline got in the way. I did deconstruct the vba and rebuild it. And it does work correctly now.

Larry Wilson
LWilson@LJBinc.com

Answer Verified By: Beebe Ray
Cancel
Vote Up 0 Vote Down

Sign in to reply

Reject Answer

Cancel