Linda !
Yes there is a way to negate ANY set of characters for
a convert - at least if your running ASCII and not unicode:
First, make a string that contains all possible characters:
ALL = ''; FOR II = 1 TO 256;ALL := CHAR(II-1) ;
NEXT
Yes. Both machines are running XP and both programs were built on XP. The
big difference is that one was developed with Visual Basic 5 and the other
was developed with VB.NET and VS 2005. The libraries would definitely be
different between those two environments. I am just not sure what the
Hi Charles,
Native NT dlls expose the entry points to publicly exposed methods in a table.
The named methods are mapped to that table. When you link to a method in a dll,
the compiler loads the external dll, looks up your method in the table, and
actually links to it by the ordinal offset of
Hi there are many examples of setting up uniobjects.net params within the
config file, however in asp.net simply putting the UO.NET section in
web.config does not compile as it is not a defined section. So I have also
added the following
configSections
section name=UO.NET
Hi Robert,
Thank you for the explanation. I see what the error means now. All of
the copies of the unirpc32.dll that I find have the same date and size.
6/27/2005 45,056 bytes.
Here's an odd thing. I've been digging through the dependency list (VB5)
and the file list (VB.NET). VB.NET
When loading a dependent dll, the loader also tries to load all statically
linked dependent dlls of the dependent dll. What could be happening is that
either the unioledb.dll or uniobjects.dll that you are linking to is a
different version, and expects to link to a different unirpc32.dll. If
Hello,
I use:
configSections
sectionGroup name=UO.NET
section name=General
type=System.Configuration.DictionarySectionHandler/
section name=ConnectionPooling
type=System.Configuration.DictionarySectionHandler/
/sectionGroup
/configSections
Symeon:
I take it Jacques' answer was what you needed?
Bill
Jacques G. said the following on 8/24/2010 9:21 AM:
Hello,
I use:
configSections
sectionGroup name=UO.NET
section name=General
OK. Turned out to be a really easy fix. I added the two DLLs to the
dependency table while making the deployment package. Seems obvious now,
except I swear they were never there before. This app has been in use for
years and I have modified it a dozen times. This never came up before. I
If they were in your path before, everything would have worked. Dependencies
have been known to drive programmers crazy. They used to call it dll-hell.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of
10 matches
Mail list logo