Comments by derekbeacroft (Top 6 by date)

Ok I will try again.

I have the same .vb code module used in two places
the g_Datafile is defined as a global public in the top of the dll Module code
eg.
Module Soft_Routines
Public g_DataFile As String


and again it appears identically in my normal app

Module Soft_Routines
Public g_DataFile As String

my declaration is Public which I assume is affecting the way it is addressable from my dll to other apps, if I remove the imports UserSecurity the clash is removed.

I understand the referencing and what imports achieves, im having problems with the scope of the variable within the application and how to keep the functionality of a global within the dll but hidden from other apps.

it may be my declaration needs to change or move them into a private module

I should note the application compiles and runs fine g_DataFile also functions as expected, its just using it in the immediate window I have issues where the error appears an only in the module that has the imports statement (obviously referring to the dll with clashing names).

Well that's a useful comment, I hope some of the other people on this forum are a little more helpful.

"Learn it and come back"

Why do you think this forum exists ?


But thanks for your comments no mater how unhelp full you are.

Ahh Namespaces, I come from 12yrs vb6 and 2 yr .Net so not so great on namespaces
my dll uses a RootNamespace of "UserSecurity"

My app uses a Rootnamespace of "QuotesApplication"

in my app I add "Imports UserSecurity"

Not really sure how to resolve it though, the vars are public in the module Code, should I move them elsewhere ??

Dez

Ok after pulling apart the forms with notepad etc

looks like the coder was using a Datagrid. This seems to allow colouring in the grid

dataGridViewSchedule(startcell, endcell).Style.BackColor = Color.BurlyWood

So the referances to the code has helped
Thanks