Tracing Links Problem and Conversion Errors

[JamesDC]

Hey all,

I have two problems with trying to upgrade an access file, not written by myself.

This first is that I'm trying to change the items on a dropbox list, and they are linked with the following code:

SELECT DISTINCTROW [Processing Data].[ID], [Processing Data].[Number], [Processing Data].[Products] FROM [Processing Data];

My problem is that I cannot find any table called Processing Data. Are there other places that I could look to try to find this? Or is there a way to open the link from inside the properties box for the dropbox?

My second question is concerning these conversion errors that appeared in the Table menu when the database was converted from Access 200 to Access 2002. They seem to each contain a small error comment, and I'm not sure if I should delete them.

Thanks in advance for any help you can provide,

James

[NeoPa]

Look for a command button whose name is Command176 (Don't rely on the text in the associated label but look for the Name of the control itself).

[MMcCarthy]

Sorry about that,

the line that the error came up on is :
ItemNum.SetFocu s

Where ItemNum is highlighted. The exact error is Compile Error: Variable Not Defined

I can't find any items on any of the forms that use Command176 when clicked. So I'm still looking...

Open the form in design view that this code is written behind. You should be able to tell from the top display bar which form it is. The command button will be one of the buttons on this form. Look at the properties of each button and check the name property under the Other tab to find it.

Now look for ItemNum as a textbox name on this form.

Mary

[MMcCarthy]

Snap again :D

[JamesDC]

It's like I'm talking to only 1 person with the way your two replies keep coming back...

Anyways, I searched all the buttons, comboboxes, and text boxes and could not find any trace of a Command176 being used. I did find an old un-used form though that has a text field with control source: "Item Num"

I suspect this has something to do with "ItemNum" in the code, but the space is creating a problem...

[MMcCarthy]

It's like I'm talking to only 1 person with the way your two replies keep coming back...

Anyways, I searched all the buttons, comboboxes, and text boxes and could not find any trace of a Command176 being used. I did find an old un-used form though that has a text field with control source: "Item Num"

I suspect this has something to do with "ItemNum" in the code, but the space is creating a problem...

Comment out all the code with an apostrophe at the beginning of each line and this will stop the error. You can always visit it again if it turns out that something is no longer working.

Mary

[MMcCarthy]

It's like I'm talking to only 1 person with the way your two replies keep coming back...

Hey Ade -

Now I'm getting worried. If we start thinking alike we're in big trouble. :D

Mary

[NeoPa]

Open the form in design view that this code is written behind. You should be able to tell from the top display bar which form it is. The command button will be one of the buttons on this form. Look at the properties of each button and check the name property under the Other tab to find it.

Now look for ItemNum as a textbox name on this form.

Mary

Snap again :) (Ooops - didn't catch all the updates in-between. Now I have it's frightening how similar our answers are :().
Alternatively, to get to the design of the form whose code is displayed in the VBA window, hit Alt-F11. This should switch you across to the main Access window with that object selected.

[NeoPa]

In that case it is worth your while going through the errors and making sure all issues have been dealt with. Any issues not dealt with are very likely to bite you on the 4rse later on :(
To be sure that it is in a reliable state I would also recommend compiling the database completely before continuing. This will highlight any errors in the code that it discovers can't work. This is a very handy tool for finding and fixing errors.

Good luck with the task.
My nether regions are currently a little sore as I just discovered some more problems related to a database upgrade I did recently to A2K (And I did compile and test etc before releasing it).

I was hoping it wouldn't get to this stage, but in my recent experience, I had to comment out all offending code when I upgraded (I had to upgrade from 95 to 97 and then again on to 2K) and I only revisited the code to fix it all up when it was fully upgraded.
My problem was mainly due to CurrentDB not being liked by Access97. Access 2K liked it fine though so I just re-instated the lines when it got that far.
In your case you'll probably find that there's just a whole bunch of extraneous code which was just never tidied up properly (or at all). As the lady says - just comment it out unless and until you find you actually need it.

[JamesDC]

I've commented out that entire command176 block of code and now there are no errors on debugging. I'm going through the database now to determine if anything was hurt by doing this. So far everything is working fine...

[NeoPa]

Glad to hear that James.
Upgrading can be a headache as you've found out, but after the learning curve things do settle down a bit. Of course taking over someone else's sloppy work is never fun - it's hard enough when they are relatively tidy.