using combo boxe instead of default record navigators

[complexx]

I have built an example of a form that I am working on. My original design used the default record navigator bars that are setup when you use the wizard to create the form. I would like to remove those bars and use the linked combo boxes that I have placed onto the form instead.

My end all goal is to have those two record navigation bars completely gone from the form and have the combo boxes perform the same function they were used for.

I would like to keep the data entry portion of the form the same because I like the design and I like that I can limit it to data entry only so theres no chance that the users will accidentally modify existing data. However, if you have a different method of entering the data that will still provide me with the protection of "data entry only" that will be welcomed.

 

[CraigDolphin]

Why don't you just set the dataentry property of the form to yes? This restricts the form to entering new data only and will not allow the user to see data entered in previous sessions.

 

[complexx]

That is what I have done. But my main concern is ease of use. The problem I am having is that my company has ove 100 different customers and each customer could have anywhere from 1-5 systems for example. So, worst case scenario, for my secretary to select a specific system to input data to, she might have to click 250 times on that record navigator bar on the bottom of the form in order to find the right customer.

I want to eliminate those horrible record navigators and use combo boxes instead. BUt I can't seem to figure out how to do that and keep the format for inputing the data the way it is currently.

 

[RuralGuy]

Here's your db back with some changes. See if this is what you had in mind.

 

[complexx]

Great! Thats exactly what I was trying to accomplish.

It works fine in the sample database that you sent to me, however when I import it to the main database that I have, I get the following error when trying to open it.

"Invalid Procedure call or argument" and directs me to the form load in the debugger.

 

[RuralGuy]

The debugger should actually highlight a line it does not like. What is the code that is highlighted? How about posting all of the code in the Load event? Before trying to run your forms you should compile everything and see if there are any errors. One error can throw everything off. Do you know how to do that? <ALT> F11 and then Debug>Compile.

 

[complexx]

The debugger should actually highlight a line it does not like. What is the code that is highlighted? How about posting all of the code in the Load event? Before trying to run your forms you should compile everything and see if there are any errors. One error can throw everything off. Do you know how to do that? <ALT> F11 and then Debug>Compile.

I'll give that a shot.

 

[complexx]

So I started up the debugger and tried to compile and it won't. As soon as I attempt the compile, I get the same error and it just points me to the Form Load procedure for one of the forms. Any chance of emailing you the database so you can look at it at your liesure?

 

[RuralGuy]

Have you tried Tools>Database Utilities>Compact and Repair Database and then zip the db. Is it too big to post here? If so then you can send it to Rural Guy at Wild Blue dot Net without the spaces and I'll take a look at it.

 

[complexx]

Wow that compress and repair is great!

It should be attached to this post.

 

[RuralGuy]

Something strange was going on so I created a new blank db and imported everything into it. Now it compiles without error. I didn't change anything else other than make sure all of your code modules had Option Explicit at the top. Access can get that way sometimes.

 

[complexx]

Thank you for the help. The database is now functioning well.

 

[RuralGuy]

Excellent! Glad you got things working.