Bulk Storage Location

Hi,
Basically, I think you're wanting to use the 'Bulk Storage Location' as a default where items are initially added and then can be moved to a different location at some future point (assuming I've understood the issue correctly).
With respect, it seems to me that you're overcomplicating things.
1.  Isn't a 'bulk storage location' just like the other storage locations?  I'm not sure why you need to treat it differently by using a separate form.
2.  I don't understand your point about locations needing to be "....opened and gone through".  I think this could be addressed by having better search criteria on your main form.
I've taken your existing project and used bits from old projects of mine to hopefully give you an idea of how it might work and have included the above ideas (and some others) in the attachment.
Specifically
1.  The additional search criteria on Form1 gives you the option to filter for anything including 'Bulk Storage' from the 'Location' combobox (and any combination of search criteria).
2.  All the search criteria are now 'interactive' so start working as soon as anything is entered.
3.  All the search criteria are automatically wild-carded so you don't need to enter an exact match.
4.  I didn't see the need for a separate form for updating the 'weblinks' so it's now done on Form1.
5.  On Form2, 'Bulk Storage' is the default location;  this way, you can simply add items to your inventory and accept the default - but it also gives you the option to enter a specific location if you know it. 
6.  You might want to consider using 'parent comboboxes' to narrow down your choices to make it easier for the User and to reduce data entry mistakes.
7.  The barcode is now generated automatically once all of the required elements (location, storage type, shelf and bin) have been entered.
8.  The setting up of 'reference' data (ie location, bin, shelf etc) is now done all on one form using tab-sheets and editable tablegrids (to reduce the number of forms in your application).
Apologies but I've removed a lot of your script (I wanted to highlight where I'd made changes / suggestions) but it should just be a cut/paste exercise from your old project to re-insert them.
Anyway, hopefully this has given you some ideas so you can move your project forward.
Regards,
Derek.

Hi,
Maybe it would be easier if you put together an application specifically based on your 'bulk holding' proposal and then list out the things that aren't working as you'd like them.
From your description, I understand that you want
1.  one or a number of bins
2.  each bin can have one or a number of categories.
But after that, I'm not clear what you're trying to achieve.  Specifically,
3.  how do you identify discrete Parts in the first place - do they have their own QR/Bar codes?  So are you trying to use additional QR/Bar codes to identify WHERE parts are stored?  If so, I don't understand what advantage a QR/Bar code gives you rather than simply using a label with a Bin ID /  Category ID.
4.  there seems a contradiction when you write 'generates one label for the bin' but then you write '...label title - electrical or plumbing'.  So wouldn't that be a label per Category not per Bin?   
Anyway, I'm sure that MVD will be able to handle what you're trying to achieve (most of it sounds like 'standard' functionality).   But as with everything, it all starts with a clear understanding of the process and then making sure that your data schema supports that process.
None of the above is a criticism but the more accurately people understand your issues, the more focused and relevant are any fixes and suggestions that people may offer.
Regards,
Derek.