[AccessD] Ambiguous Name

I can't agree.  Global variables break the whole model of structured  
programming.  In many ways they are worse than goto statements.

Sent from my Verizon Wireless Phone

-----Original message-----
From: Gustav Brock <Gustav at cactus.dk>
To: accessd at databaseadvisors.com
Sent: Tue, Sep 20, 2011 14:51:24 GMT+00:00
Subject: Re: [AccessD] Ambiguous Name

Hi Steve

Nothing wrong with global variables. 
Trouble is always located at those handling these (the programmer!).

/gustav


>>> steve at goodhall.info 20-09-2011 01:33:24 >>>
Yet another reason to never use global variables.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com 
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Ralf Lister
Sent: Monday, September 19, 2011 5:19 PM
To: accessd at databaseadvisors.com 
Subject: [AccessD] Ambiguous Name

Hello all,

I work with Access 2007.

Lately I ran into a problem I don't know how to solve: By running the code I
got an error message "Ambiguous Name was detected: gsngAportesSR" ("Se ha
detectado un nombre ambiguo: gsngAportesSR"). I searched the whole code
looking for gsngAportes defined by two different data types (e.g. Public
gsngAportesSR As Single, and then also Public gsngAportesSR As Integer), but
without success.

Does anyone of you know how to fix this problem?

I should say that gsngAportesSR is a global variable with data type Single.

Thanks and Saludos
Ralf Lister
La Paz, Bolivia


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com