COMPILER WRONG !!!

Hi Vandal ,
i am Access user for 5 Years
before FoxPro for 5 years
My MDB ( ~5MB, of text code, i wrote for 5 years...)
It is dailly running over night 15 hours, error free

I do not have ANY time for stupid Questions,
*********************************

OK, i can try it with printer

but the question is a have 10 another databases,
with this CRAZY-line , and it is O.K. WHY ????

this was an Error in ONLY ONE (WRONG) Database.
I does not have changed this line of code !!!!!
Todays build is O.K., Why ??????????

Hi, the same command
SetOption "Left margin", "0.1"""
while running..error, empty argument...WHY ?
in Immediate window(while code running) the same OK !!!!
and the same code-line in another databse build...OK !!!!, WHY ???

I do not have time for stupid Questions,
*********************************
My MDB ( ~5MB, of text code, i wrote for 5 years, it was running
in Access 2000 wounderful, but now is there something WRONG, and it is really
ANNOYING such CRAZY errors !!!


"AccessVandal via AccessMonster.com" wrote:

No intention of offending anyone.

Maybe you’re posting to the wrong forum? What CODE? Da Vinci Code? That book
was use to be collecting dust in bookstores back in the early 70s.

PACALA_BA wrote:
Hi, In the CODE are NO-PROGRAMMERS-ERRORS (my Opinion)
This happens Allways, in 1-2 code-places (most case), sometimes over 10.
After Pseudo-line-edit (Before/After the same)
...it is ALL-OK
And Problem CODE is allways in ANOTHER-Code-Place
BIG-PROBLEM is this wrong-compiler-example
Here is the CORE of CODE....or something else missing ?
*****************************************
http://i34.tinypic.com/71sdq8.jpg ;

I can place the whole code here , but you will see Nothing ....(my Opinion)
There must be Something else WRONG...

After Compile is all OK, NO-Errors (But it is NOT REALLY TRUE !!),

--
Please Rate the posting if helps you

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200810/1

Todays Problem

ln_Perm = IIf(bAllPerm, oPerm.AllPermissions, oPerm.Permissions)
? err, err.Description (function: ap_GetPermissions)
7,Out of memory
immediate window (while runnig) ...O.K. WHY ???

How can i check the Error, it is Really Out of memory ??
****************************************
When i ignore the error,and continue, all other is running O.K.
After database rebuild, **nothing changed*** NONE Errors, WHY ???
************************************************** *

In the Task manager:
msAccess, MEMORY usage ~50MB
peak memory usage ~60MB
virtual memory ~40MB

ln_Perm = IIf(bAllPerm, oPerm.AllPermissions, oPerm.Permissions)
? err, err.Description (function: ap_CheckPermissions)
7,Out of memory
immediate window (while runnig) ...O.K. WHY ???

But i can step through the code ,ONLY THIS ONE command is err=7,...
ln_Perm = IIf(bAllPerm, oPerm.AllPermissions, oPerm.Permissions)

Full code of functions:
Function ap_GetPermissions(strUserName$, strObjectName$, eObjType As
eAP_ObjectType, Optional bNewObj As Boolean = False, Optional bAllPerm As
Boolean = True, Optional bRetOK As Boolean, Optional eDB As eDBEnum =
eDB__FILEName, Optional eDV_XXX As eDVEnum, Optional nDBTYPE As eDBTypeEnum =
EDB_CUR, Optional cDataBaseFullName$ = vbNullString, Optional nDBCounter As
eDBCounterEnum = eDBC_1, Optional cNote$ = "MSysDb, bAllPerm = (USER/GROUP)")
As Long
On Error GoTo XPAC_CHYBA: Dim lc__proc_meno$, strConnect$, lc_ObjName$,
lc_UserName$, lc_DBFile$, ll_ERR As Boolean, DB As DAO.Database, con As
DAO.Container, doc As DAO.Document, ln_Perm&, oPerm As Object, ln_Ret&,
strObjectType$: lc__proc_meno$ = "ap_GetPermissions": strObjectType =
EnumAP_ObjectType(eObjType): lc_DBFile = Nz(cDataBaseFullName): If
(Len(lc_DBFile) = 0) Then lc_DBFile = DDF_CURRENT
Set DB = DDF_GET_DB_REF(cDataBaseFullName:=lc_DBFile): lc_ObjName =
strObjectName: lc_ObjName = IIf(((Len(lc_ObjName) = 0) And (eObjType =
eApOType_DDF)), "MSysDb", lc_ObjName): Set con =
DB.Containers(strObjectType): con.Inherit = bNewObj: If bNewObj Then Set
oPerm = con
If Not bNewObj Then Set doc = con.Documents(lc_ObjName): Set oPerm = doc
lc_UserName = IIf((Len(strUserName) = 0), CurrentUser, strUserName):
oPerm.UserName = lc_UserName
ln_Perm = IIf(bAllPerm, oPerm.AllPermissions, oPerm.Permissions)
If Not DB Is Nothing Then DB.Close
xPAC_KONIEC: Set oPerm = Nothing: Set doc = Nothing: Set con = Nothing: Set
DB = Nothing: ap_GetPermissions = ln_Perm: bRetOK = (Not ll_ERR): Exit
Function
XPAC_CHYBA: ll_ERR = True: ln_Perm = -1: ERROR_RAISE lc__proc_meno, "Err: "
& Err & ", " & Err.Description & vbCrLf & "PROC: '" & lc__proc_meno & "'":
GoTo xPAC_KONIEC
End Function

Function ap_CheckPermissions(strUserName$, strObjectName$, eObjType As
eAP_ObjectType, fPerm As DAO.PermissionEnum, Optional bNewObj As Boolean =
False, Optional bAllPerm As Boolean = True, Optional bRetOK As Boolean,
Optional eDB As eDBEnum = eDB__FILEName, Optional eDV_XXX As eDVEnum,
Optional nDBTYPE As eDBTypeEnum = EDB_CUR, Optional cDataBaseFullName$ =
vbNullString, Optional nDBCounter As eDBCounterEnum = eDBC_1, Optional cNote$
= "MSysDb, bAllPerm = (USER/GROUP)") As Boolean
On Error GoTo XPAC_CHYBA: Dim lc__proc_meno$, ll_ERR As Boolean,
lc_ObjName$, lc_UserName$, ll_RET As Boolean, strConnect$, oPerm As Object,
ln_Perm&, lc_DBFile$, DB As DAO.Database, con As DAO.Container, doc As
DAO.Document, strObjectType$: lc__proc_meno$ = "ap_CheckPermissions":
strObjectType = EnumAP_ObjectType(eObjType): lc_DBFile =
Nz(cDataBaseFullName): If (Len(lc_DBFile) = 0) Then lc_DBFile = DDF_CURRENT
Set DB = DDF_GET_DB_REF(cDataBaseFullName:=lc_DBFile): lc_ObjName =
strObjectName: lc_ObjName = IIf(((Len(lc_ObjName) = 0) And (eObjType =
eApOType_DDF)), "MSysDb", lc_ObjName): Set con =
DB.Containers(strObjectType): con.Inherit = bNewObj: If bNewObj Then Set
oPerm = con
If Not bNewObj Then Set doc = con.Documents(lc_ObjName): Set oPerm = doc
lc_UserName = IIf((Len(strUserName) = 0), CurrentUser, strUserName):
oPerm.UserName = lc_UserName: ln_Perm = IIf(bAllPerm, oPerm.AllPermissions,
oPerm.Permissions): ll_RET = ((ln_Perm And fPerm) = fPerm): ll_RET =
IIf(((fPerm = dbSecNoAccess) And (ln_Perm dbSecNoAccess)), False, ll_RET):
If Not DB Is Nothing Then DB.Close
xPAC_KONIEC: Set oPerm = Nothing: Set doc = Nothing: Set con = Nothing: Set
DB = Nothing: ap_CheckPermissions = ll_RET: bRetOK = (Not ll_ERR): Exit
Function
XPAC_CHYBA: ll_ERR = True: ERROR_RAISE lc__proc_meno, "Err: " & Err & ", " &
Err.Description & vbCrLf & "PROC: '" & lc__proc_meno & "'": GoTo xPAC_KONIEC
End Function

"John W. Vinson" wrote:

On Thu, 2 Oct 2008 08:46:29 -0700, PACALA_BA
wrote:

I have now shorten my LONG lines of code to 1/2 Length
The Maximum size = 1024 char (says Microsoft)
But It seems that the RECOMMENDED Maximum Size is NOT 1024 char

I am also MASSIVE using the double dot ':' operator
Before January 2008 , i have NONE such Problems
May be i try to recreate my code to VERY SHORT LINES.
But it is an terible thing
if (cond1 ) then x = x+ 1:y = y+1:if (cod2) then x= x-1:y = y+2:....

WHY are you trying to put all the code on one line?

It's both easier to read and easier for the compiler if you do it the normal
way:

If (cond) Then
X = X + 1
Y = Y + 1
Elseif (Cond2) Then
X = x -1
Y = Y +2
End If

and i am using ONE line Select case
Select case a:case 1: x=1:case2:x=2:case else:x=10:end select

Again:

Select Case A
Case 1
X = 1
Case 2
X = 2
Case Else
X = 10
End Select

This may be an Problem (? !)

i am Allways making the same
some Little changes in MDB ~9MB
than Saveastext/Load asText, make MDE
And it works NOT 100% Error free.
the succes rate is about 30-50 %.
When i create the OK-(NONE-CRASH)MDE,
than it works WONDERFULL.....
All Access Crashes, Reported to MICROSOFT
since January 2008 about 500 CRASHES !!
*******************************
I do NOT Know the Result of this Crashes....
This MUST say MICROSOFT....
(see.....Why shoud i report to microsoft, or NOT ?)

If you're assuming that posting in this newsgroup is "reporting to Microsoft"
you should be aware that it is NOT. These newsgroups are peer support groups;
everyone who answers questions here is an unpaid volunteer. Even the
occasional posts from Microsoft employees are (as far as I know) on their own
time.

I do *not* think you have a bug.

I think you have a very individual and probably flawed programming style, for
reasons which I do not understand.

Try writing your code without multiple lines per line, and without hugely long
single lines. I honestly believe it will work better.
--

John W. Vinson [MVP]

Why bother asking us for advice if you're not going to take it?

Many different people have to you not to use the colon approach: to put no
more than one statement of code per line, and you persist in doing that.

Do you believe that making your code so difficult to read is going to make
your application smaller? You might be saving a few bytes by avoiding
carriage returns and line feeds, but it is not going to reduce your overall
size appreciably.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"PACALA_BA" wrote in message
...
Todays Problem

I restructured your first funxction. See my comments about possible
errors.

Function ap_GetPermissions( _
strUserName$, _
strObjectName$, _
eObjType As eAP_ObjectType, _
Optional bNewObj As Boolean = False, _
Optional bAllPerm As Boolean = True, _
Optional bRetOK As Boolean, _
Optional eDB As eDBEnum = eDB__FILEName, _
Optional eDV_XXX As eDVEnum, _
Optional nDBTYPE As eDBTypeEnum = EDB_CUR, _
Optional cDataBaseFullName$ = vbNullString, _
Optional nDBCounter As eDBCounterEnum = eDBC_1, _
Optional cNote$ = "MSysDb, bAllPerm = (USER/GROUP)" _
) As Long
On Error GoTo XPAC_CHYBA

Dim lc__proc_meno$, strConnect$, lc_ObjName$, _
lc_UserName$, lc_DBFile$, ll_ERR As Boolean, _
DB As DAO.Database, con As DAO.Container, _
doc As DAO.Document, ln_Perm&, oPerm As Object, _
ln_Ret&, strObjectType$

lc__proc_meno$ = "ap_GetPermissions"
strObjectType = EnumAP_ObjectType(eObjType)
lc_DBFile = Nz(cDataBaseFullName)

If (Len(lc_DBFile) = 0) Then lc_DBFile = DDF_CURRENT
Set DB = DDF_GET_DB_REF(cDataBaseFullName:=lc_DBFile) '-- error
here?

'lc_ObjName = strObjectName
'lc_ObjName = IIf(((Len(lc_ObjName) = 0) _
' And (eObjType = eApOType_DDF)), "MSysDb", lc_ObjName)
' above translates to below. do you really want lc_ObjName = "" ?
If len(strObjectName) 0 then
If eObjType = eApOType_DDF then
lc_ObjName = "MSysDb"
else
lc_ObjName = ""
end if
lc_ObjName = strObjectName
end if

Set con = DB.Containers(strObjectType)
con.Inherit = bNewObj

'what is below supposed to do? The way I understand,
'it always sets operm = doc.

If bNewObj Then Set oPerm = con
If Not bNewObj Then Set doc = con.Documents(lc_ObjName)
Set oPerm = doc '--- this overrides what you did above.
' above translates to below. do you really want lc_ObjName = "" ?
If bNewObj Then
Set oPerm = con
else
Set doc = con.Documents(lc_ObjName)
end if
Set oPerm = doc '-- I think you want this above the end if


lc_UserName = IIf((Len(strUserName) = 0), CurrentUser, strUserName)
oPerm.UserName = lc_UserName
ln_Perm = IIf(bAllPerm, oPerm.AllPermissions, oPerm.Permissions)
If Not DB Is Nothing Then DB.Close

xPAC_KONIEC:
Set oPerm = Nothing
Set doc = Nothing
Set con = Nothing
Set DB = Nothing
ap_GetPermissions = ln_Perm
bRetOK = (Not ll_ERR)
Exit Function

XPAC_CHYBA:
ll_ERR = True
ln_Perm = -1
ERROR_RAISE lc__proc_meno, "Err: " & Err & ", " _
& Err.Description & vbCrLf & "PROC: '" & lc__proc_meno & "'"
GoTo xPAC_KONIEC '-- resume xPAC_KONIEK ???
End Function


=?Utf-8?B?UEFDQUxBX0JB?= wrote
in :

Todays Problem

ln_Perm = IIf(bAllPerm, oPerm.AllPermissions, oPerm.Permissions)
? err, err.Description (function: ap_GetPermissions)
7,Out of memory
immediate window (while runnig) ...O.K. WHY ???

How can i check the Error, it is Really Out of memory ??
****************************************
When i ignore the error,and continue, all other is running O.K.
After database rebuild, **nothing changed*** NONE Errors, WHY ???
************************************************** *

In the Task manager:
msAccess, MEMORY usage ~50MB
peak memory usage ~60MB
virtual memory ~40MB

ln_Perm = IIf(bAllPerm, oPerm.AllPermissions, oPerm.Permissions)
? err, err.Description (function: ap_CheckPermissions)
7,Out of memory
immediate window (while runnig) ...O.K. WHY ???

But i can step through the code ,ONLY THIS ONE command is
err=7,... ln_Perm = IIf(bAllPerm, oPerm.AllPermissions,
oPerm.Permissions)

Full code of functions:
Function ap_GetPermissions(strUserName$, strObjectName$, eObjType
As eAP_ObjectType, Optional bNewObj As Boolean = False, Optional
bAllPerm As Boolean = True, Optional bRetOK As Boolean, Optional
eDB As eDBEnum = eDB__FILEName, Optional eDV_XXX As eDVEnum,
Optional nDBTYPE As eDBTypeEnum = EDB_CUR, Optional
cDataBaseFullName$ = vbNullString, Optional nDBCounter As
eDBCounterEnum = eDBC_1, Optional cNote$ = "MSysDb, bAllPerm =
(USER/GROUP)") As Long
On Error GoTo XPAC_CHYBA: Dim lc__proc_meno$, strConnect$,
lc_ObjName$, lc_UserName$, lc_DBFile$, ll_ERR As Boolean, DB As
DAO.Database, con As DAO.Container, doc As DAO.Document, ln_Perm&,
oPerm As Object, ln_Ret&, strObjectType$: lc__proc_meno$ =
"ap_GetPermissions": strObjectType = EnumAP_ObjectType(eObjType):
lc_DBFile = Nz(cDataBaseFullName): If (Len(lc_DBFile) = 0) Then
lc_DBFile = DDF_CURRENT Set DB =
DDF_GET_DB_REF(cDataBaseFullName:=lc_DBFile): lc_ObjName =
strObjectName: lc_ObjName = IIf(((Len(lc_ObjName) = 0) And
(eObjType = eApOType_DDF)), "MSysDb", lc_ObjName): Set con =
DB.Containers(strObjectType): con.Inherit = bNewObj: If bNewObj
Then Set oPerm = con
If Not bNewObj Then Set doc = con.Documents(lc_ObjName): Set oPerm
= doc lc_UserName = IIf((Len(strUserName) = 0), CurrentUser,
strUserName): oPerm.UserName = lc_UserName
ln_Perm = IIf(bAllPerm, oPerm.AllPermissions, oPerm.Permissions)
If Not DB Is Nothing Then DB.Close
xPAC_KONIEC: Set oPerm = Nothing: Set doc = Nothing: Set con =
Nothing: Set DB = Nothing: ap_GetPermissions = ln_Perm: bRetOK =
(Not ll_ERR): Exit Function
XPAC_CHYBA: ll_ERR = True: ln_Perm = -1: ERROR_RAISE
lc__proc_meno, "Err: " & Err & ", " & Err.Description & vbCrLf &
"PROC: '" & lc__proc_meno & "'": GoTo xPAC_KONIEC
End Function

Function ap_CheckPermissions(strUserName$, strObjectName$,
eObjType As eAP_ObjectType, fPerm As DAO.PermissionEnum, Optional
bNewObj As Boolean = False, Optional bAllPerm As Boolean = True,
Optional bRetOK As Boolean, Optional eDB As eDBEnum =
eDB__FILEName, Optional eDV_XXX As eDVEnum, Optional nDBTYPE As
eDBTypeEnum = EDB_CUR, Optional cDataBaseFullName$ = vbNullString,
Optional nDBCounter As eDBCounterEnum = eDBC_1, Optional cNote$
= "MSysDb, bAllPerm = (USER/GROUP)") As Boolean
On Error GoTo XPAC_CHYBA: Dim lc__proc_meno$, ll_ERR As Boolean,
lc_ObjName$, lc_UserName$, ll_RET As Boolean, strConnect$, oPerm
As Object, ln_Perm&, lc_DBFile$, DB As DAO.Database, con As
DAO.Container, doc As DAO.Document, strObjectType$: lc__proc_meno$
= "ap_CheckPermissions": strObjectType =
EnumAP_ObjectType(eObjType): lc_DBFile = Nz(cDataBaseFullName): If
(Len(lc_DBFile) = 0) Then lc_DBFile = DDF_CURRENT Set DB =
DDF_GET_DB_REF(cDataBaseFullName:=lc_DBFile): lc_ObjName =
strObjectName: lc_ObjName = IIf(((Len(lc_ObjName) = 0) And
(eObjType = eApOType_DDF)), "MSysDb", lc_ObjName): Set con =
DB.Containers(strObjectType): con.Inherit = bNewObj: If bNewObj
Then Set oPerm = con
If Not bNewObj Then Set doc = con.Documents(lc_ObjName): Set oPerm
= doc lc_UserName = IIf((Len(strUserName) = 0), CurrentUser,
strUserName): oPerm.UserName = lc_UserName: ln_Perm =
IIf(bAllPerm, oPerm.AllPermissions, oPerm.Permissions): ll_RET =
((ln_Perm And fPerm) = fPerm): ll_RET = IIf(((fPerm =
dbSecNoAccess) And (ln_Perm dbSecNoAccess)), False, ll_RET):
If Not DB Is Nothing Then DB.Close
xPAC_KONIEC: Set oPerm = Nothing: Set doc = Nothing: Set con =
Nothing: Set DB = Nothing: ap_CheckPermissions = ll_RET: bRetOK =
(Not ll_ERR): Exit Function
XPAC_CHYBA: ll_ERR = True: ERROR_RAISE lc__proc_meno, "Err: " &
Err & ", " & Err.Description & vbCrLf & "PROC: '" & lc__proc_meno
& "'": GoTo xPAC_KONIEC End Function

"John W. Vinson" wrote:

On Thu, 2 Oct 2008 08:46:29 -0700, PACALA_BA
wrote:

I have now shorten my LONG lines of code to 1/2 Length
The Maximum size = 1024 char (says Microsoft)
But It seems that the RECOMMENDED Maximum Size is NOT 1024 char

I am also MASSIVE using the double dot ':' operator
Before January 2008 , i have NONE such Problems
May be i try to recreate my code to VERY SHORT LINES.
But it is an terible thing
if (cond1 ) then x = x+ 1:y = y+1:if (cod2) then x= x-1:y =
y+2:....

WHY are you trying to put all the code on one line?

It's both easier to read and easier for the compiler if you do it
the normal way:

If (cond) Then
X = X + 1
Y = Y + 1
Elseif (Cond2) Then
X = x -1
Y = Y +2
End If

and i am using ONE line Select case
Select case a:case 1: x=1:case2:x=2:case else:x=10:end select

Again:

Select Case A
Case 1
X = 1
Case 2
X = 2
Case Else
X = 10
End Select

This may be an Problem (? !)

i am Allways making the same
some Little changes in MDB ~9MB
than Saveastext/Load asText, make MDE
And it works NOT 100% Error free.
the succes rate is about 30-50 %.
When i create the OK-(NONE-CRASH)MDE,
than it works WONDERFULL.....
All Access Crashes, Reported to MICROSOFT
since January 2008 about 500 CRASHES !!
*******************************
I do NOT Know the Result of this Crashes....
This MUST say MICROSOFT....
(see.....Why shoud i report to microsoft, or NOT ?)

If you're assuming that posting in this newsgroup is "reporting
to Microsoft" you should be aware that it is NOT. These
newsgroups are peer support groups; everyone who answers
questions here is an unpaid volunteer. Even the occasional posts
from Microsoft employees are (as far as I know) on their own
time.

I do *not* think you have a bug.

I think you have a very individual and probably flawed
programming style, for reasons which I do not understand.

Try writing your code without multiple lines per line, and
without hugely long single lines. I honestly believe it will work
better. --

John W. Vinson [MVP]




--
Bob Quintal

PA is y I've altered my email address.
** Posted from http://www.teranews.com **

No offence, but nobody can read your code. We are just volunteers here.

Please reply to Bob Quintal's of the outcome on this

AND THE CODE IS WRONG!!!!!!!!!!!!!!!!!
No wonder you get errors.
The format is
expression.SetOption(OptionName, Setting)
you want
printer.setoption "Left Margin", 0.1

Did you correct as suggested by Bob (notice the quotes)? What was the result?

Nobody's blaming you. Sometimes Access bombs out codes that works for years
with out problems.
It's just that we do not have time to go through every line of code.

PACALA_BA wrote:
Hi Vandal ,
i am Access user for 5 Years
before FoxPro for 5 years
My MDB ( ~5MB, of text code, i wrote for 5 years...)
It is dailly running over night 15 hours, error free

I do not have ANY time for stupid Questions,
*********************************

OK, i can try it with printer

but the question is a have 10 another databases,
with this CRAZY-line , and it is O.K. WHY ????

this was an Error in ONLY ONE (WRONG) Database.
I does not have changed this line of code !!!!!
Todays build is O.K., Why ??????????

Hi, the same command
SetOption "Left margin", "0.1"""
while running..error, empty argument...WHY ?
in Immediate window(while code running) the same OK !!!!
and the same code-line in another databse build...OK !!!!, WHY ???

I do not have time for stupid Questions,
*********************************
My MDB ( ~5MB, of text code, i wrote for 5 years, it was running
in Access 2000 wounderful, but now is there something WRONG, and it is really
ANNOYING such CRAZY errors !!!

No intention of offending anyone.

[quoted text clipped - 15 lines]

After Compile is all OK, NO-Errors (But it is NOT REALLY TRUE !!),

--
Please Rate the posting if helps you

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200810/1

=?Utf-8?B?UEFDQUxBX0JB?= wrote
in :

I do not have time for stupid Questions

I don't understand what you mean by that, as from where I sit, it's
*you* who has been asking stupid questions. If you can't answer
requests for clarifications from those who are trying to help you,
then you don't deserve their assistance.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

=?Utf-8?B?UEFDQUxBX0JB?= wrote
in :

Hi, the same command
SetOption "Left margin", "0.1"""
while running..error, empty argument...WHY ?
in Immediate window(while code running) the same OK !!!!
and the same code-line in another databse build...OK !!!!, WHY ???

I do not have time for stupid Questions,
My MDB ( ~5MB, of text code, i wrote for 5 years, it was running
in Access 2000 wounderful, but now is there something WRONG, and
it is really ANNOYING such CRAZY errors !!!

You posted this exact response to another post. Why? Do you think
that it will get answered the second time but not the first? That it
will be clearer when we've read it twice but not when we've seen it
just once?

Sorry, but you're really behaving in a fashion that makes me want to
put you in my killfile.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

"AccessVandal via AccessMonster.com" u18947@uwe wrote in
news:8b624ee03f08c@uwe:

Sometimes Access bombs out codes that works for years
with out problems.

This is particularly the case when you upgrade versions.

And it is often an indication that you've been following very poor
development practices in the past.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

=?Utf-8?B?UEFDQUxBX0JB?= wrote
in :

Full code of functions:

[gibberish code without line breaks deleted]

I have not time to figure out what the hell that garbage is. If you
can't format your posts in a manner that is readable, then you're
not going to get any help.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Nah..than, how do you account a simple default value on a control refused to
work on Windows Vista but works with Windows XP? Make it into a MDE, it does
not work but leave as a MDB, it works. It’s just a simple default value of
“Date()�.

It’s never always true about following Access developments. Sometimes Access
croaks for no reasons. Like lines of code goes missing after compacting. Mind
you, it has nothing to do with poor code or programming and nothing to do
with upgrading at all.

David W. Fenton wrote:
This is particularly the case when you upgrade versions.

And it is often an indication that you've been following very poor
development practices in the past.

--
Please Rate the posting if helps you

Message posted via http://www.accessmonster.com