CallManager 4.2 ... UDL file

Hi,
Does anyone know how to "force" CallManager to create a UDL file? or where this file lives?
I have done a file search on the CallManager server and can't find it anywhere.
Thank you

You mean Microsoft Data Link file (*.udl)
Check out this:
http://www.drdev.net/article10.htm

Similar Messages

Where i can get or download Oxford dictionary .udl file ?

I am ganesh from Pondy. I have doubt. Where can i get Oxford dictionary .udl file?. i am using default system dictionary. Most of the words are not properly broken as in Oxford dictionary. Please help me out.

I don't know if you can get any form of the Oxford English Dictionary as a udl, but....
Remember, the dictionary InDesign choses for a particular string of text is determined by the language of that text, and this is set as a character level attribute. Is it possible you don't have the right language setting selected in the character pallet, or in your text styles?
See:
http://help.adobe.com/en_US/InDesign/6.0/WSa285fff53dea4f8617383751001ea8cb3f-6dd4a.html

How to use UDL file in Powershell script?

Hello Scripting Guys,
I have a VBScript that works great for connecting to an Oracle DB using a .UDL file. Here is the important part of the script:
Set dataconnect = CreateObject("ADODB.Connection")
Path= "File name=C:\UDLs\TEST.udl"
dataconnect.ConnectionString = Path
dataconnect.open
Set oCmd = CreateObject("ADODB.Command")
oCmd.ActiveConnection = dataconnect
oCmd.CommandText = "SYSTEM.JOB.INSERT_JOB"
oCmd.CommandType = 4
set oParam = oCmd.CreateParameter("job_name_val")
oParam.type = 200
oParam.direction = 1
oParam.size = 255
oParam.value = job_name
oCmd.Parameters.Append oParam
set oParam = oCmd.CreateParameter("description")
oParam.type = 200
oParam.direction = 1
oParam.size = 4000
oParam.value = descrip
oCmd.Parameters.Append oParam
set oParam = oCmd.CreateParameter("status_val")
oParam.type = 200
oParam.direction = 1
oParam.size = 50
oParam.value = status
oCmd.Parameters.Append oParam
oCmd.Execute
As you can see, it creates "ADODB.Connection" and "ADODB.Command" objects. Everything works as intended here.
Now, I'm trying to convert this VBScript to a Powershell script.
Here's what I have so far with my PowerShell Script (non-working, but no errors):
$job_name = $args[0]
$status = $args[1]
$descrip = $args[2]
write-host "Job Name = " $job_name
write-host "Status = " $status
write-host "Description = " $descrip
#Create an object of type: ADODB class: Connection
$objConn = New-Object -com "ADODB.Connection"
#Create Connection String
$connString = "File name=C:\UDLs\TEST.udl"
#Open the connection
$objConn.open($connString)
#Command Object
$oCmd = New-Object -com "ADODB.Command"
#Assign DB connection To Command
$oCmd.ActiveConnection = $objConn
#Set Command text
$oCmd.CommandText = "SYSTEM.JOB.INSERT_JOB"
#Set Command Type
$oCmd.CommandType = 4
#Create parameter list For Command
#Job name Parameter
$oParam1 = $oCmd.CreateParameter("job_name_val")
$oParam1.type = 200
$oParam1.direction = 1
$oParam1.size = 255
$oParam1.value = $job_name
#Append parameter list
$oCmd.Parameters.Append($oParam1)
#Description Parameter
$oParam2 = $oCmd.CreateParameter("description")
$oParam2.type = 200
$oParam2.direction = 1
$oParam2.size = 4000
$oParam2.value = $descrip
#Append parameter list
$oCmd.Parameters.Append($oParam2)
#Status Parameter
$oParam3 = $oCmd.CreateParameter("status_val")
$oParam3.type = 200
$oParam3.direction = 1
$oParam3.size = 50
$oParam3.value = $status
#Append parameter list
$oCmd.Parameters.Append($oParam3)
#Command Execution
$oCmdX = $oCmd.Execute
write-host $oCmdX
#Cleanup
#Set parameters = To NULL
$oParam1 = $null
$oParam2 = $null
$oParam3 = $null
#Set Command = To NULL
$oCmd = $null
#Close DB object
$objConn.Close()
So, not too many changes with the syntax, but it doesn't actually send the ADODB Command to the Database. I have also tried hardcoding the connection string, but no luck there either. Am I not using the right syntax with the Command object? I am fairly new
to both of these languages, so I appreciate any help/suggestions you can offer!
Thank you,
Brian

Thanks JRV.
I am now getting this error (at least some feedback from Powershell now):
Exception calling "Open" with "1" argument(s): "[Microsoft][ODBC Driver Manager
] Data source name not found and no default driver specified"
At C:\temp\JobMon.ps1:21 char:14
+ $objConn.open <<<< ($connString)
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : ComMethodTargetInvocation
The thing is, it shouldn't be using a Microsoft driver. It should be using the Oracle Client driver (which I have installed and tested successfully using TNSPing).
Do I need to declare some sort of "using System.Data.OracleClient namespace" like in C++? How would I do that in Powershell?
Thanks again,
Brian

Creating UDL file for use of HFMCopyApplication utility

I'm trying to create the UDL file on the HFM server to link to the SQL database where HFM sits.
I followed the instructions and created a new text document, rename it as extension .udl. According to the instruction, I'm supposed to double click on this new file and an data link property window will appear. But all I see is still a blank text document.
Am I missing something? In the past I always asked our application support guys to do that but now I have to figure it out myself....
Thanks!

Hi,
The reason to rename the file to .UDL is that the UDL extension should be mapped to an application that will let you make a database connection.
You either have one of two problems if double clicking on the UDL file opened in Notepad:
#1 - At some point .UDL file extensions were mapped to point to Notepad (or whatever text editor the file opened in) [I'm doubtful this is the problem]
#2 - In Windows Explorer you do not have file extensions visible; therefore, when you renamed your file, it didn't rename it the way you wanted it to. For instance instead of renaming database.txt to database.udl, you ended up with database.udl.txt This file would still open in Notepad as .TXT is associated with Notepad (or other text editor).
IF #2 is the problem, do the following:
#1 - Open a File Explorer window and navigate to the folder with the UDL file.
#2 - Click on Tools
#3 - Folder Options
#4 - Click on View
#5 - Make sure 'Hide extensions for known file types' is unchecked.
#6 - Hit OK
#7 - Refresh the File explorer window and note the filename.
#8 - If the filename is something like .UDL.txt, rename it to remove te .txt.
If #1 is the issue: (Note : I'm giving you windows 7 version which may be different than XP, but it should still be in the control panel somewhere)
#1 - Open Control Panel
#2 - Open Default Programs
#3 - Open Set Associations
(NOTE: Instead of steps 1-3 click Start and type in associations and one of the results will be to set file associations)
#4 - Locate the .UDL file extension and confirm it is set as Microsoft Data Link, OLE DB Core Services
---IF NOT set to OLE DB Core Services --
#5 - Click on Change Program
#6 - Select OLE DB Core Services from Recommended Programs List

How to write UDL file in Labview for Database connection

Hi
I am using SQL Server database. I am making connection with SQL by using UDL file. If I create Normal UDL file in windows and make connection it happens. I want to change or add some parameter Like database name. If I am changing this value by using labview, the file gets corrupted, and not able to make connection with SQL.
I want to create database by program. User should not create the database.
Kindly suggest me the proper solution.
Regards
Prabhakant Patil
[email protected]
Regards
Prabhakant Patil

It may look like a text file, but it's not a text file that uses plain-old ASCII. If you open it in Notepad you won't see anything obvious. You actually have to open the UDL file with a hex editor, and you will see the differences. Specifically:
The file starts with the header FF FE. This indicates Unicode. LabVIEW does not support Unicode.
Each characters is actually 2 bytes. Thus, the first character you see in Notepad is "[" (for the section start). In hex this is 05 for plain-old ASCII, but 05 00 for Unicode (which is what's actually in the file).
Thus, if you absolutely must write out the file using LabVIEW you will need to write it out in binary mode, inserting the 0x00 bytes, and the FF FE at the start.
Message Edited by smercurio_fc on 03-24-2010 09:39 AM

Creating and Editing .udl files in 64-bit Windows

I have not done any database work since 64-bit Windows was released. Things have changed and I lost a few hours trying to troubleshoot database connectivity. If someone else runs into the same issues, hopefully this post will save them some time.
In trying to to examine the LabVIEW example database and UDL file:
C:\Program Files (x86)\National Instruments\LabVIEW 2010\examples\database\LabVIEW.mdb
and
C:\Program Files (x86)\National Instruments\LabVIEW 2010\examples\database\LabVIEW.udl
I copied them to a new location and found out that simply double-clicking on the UDL to view how it is configured results in an error: "Provider cannot be found. Ensure that the provider has been installed properly." This should normally bring up a UDL properties dialog/utility.
The reason for this error is that 32-bit and 64-bit OLE DB providers are carried separately in 64-bit Windows installation (even if you are using 32 bit LabVIEW).
To view and test the UDL's configuration using the windows tool, you'll need to open up a command box, and paste this text to run the 32-bit version of the ODBC Data Source Administrator:
C:\Windows\syswow64\rundll32.exe "C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll",OpenDSLFile C:\Program Files (x86)\National Instruments\LabVIEW 2010\examples\database\LabVIEW.udl
Change the path to your own UDL file. It is advised NOT to modify the original LabVIEW example UDL. Just exit the properties dialog without making changes if you open up the utility on the LabVIEW original.
This trick can be helpful if you want to use a copy of the example LabVIEW database in your own application for testing or troubleshooting. Simply copy the database and the .udl file to a new location (rename both if desired), then edit the .udl copy as necessary (modify the paste-text above as needed for the new file's location).
This will also allow you to connect the new UDL to a different 32-bit OLE provider using the UDL "Data Link Properties" utility provided within the Windoze O/S.
This trick may also be necessary if you have installed OLE providers in 32-bit mode you wish to use and cannot find the providers using the normal 64-bit ODBC Data Source Administrator that is launched by default.
References:
Create a New UDL File (MSDN)
Edit a 32-bit UDL (MSDN)
Windows KB Article on 32/64 bit ODBC

I seem to have fixed the issue...
I used C:\Windows\SysWOW64\odbcad32.exe to create a file DSN, then created a new database with that DSN. I then imported the data from my other database and that seems to work correctly.
Hope this helps someone else.

Open .udl File

Hello,
I'm trying to open an .udl file to use the third line as the connection
string in the LabSQL. Using the notepad I get this information from the
file:
[oledb]
; Everything after this line is an OLE DB initstring
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;User ID=selco;Initial Catalog=selco;Data Source=STM
But if I use Labview to open the file I get something like this:
[ o l e d b ]
; E v e r y t h i n g a f t e r t h i
s l i n e i s a n O L E D B i n i t
s t r i n g
P r o v i d e r = S Q L O L E D B . 1 ; I n t e g r a t e d
S e c u r i t y = S S P I ; P e r s i s t   S e c u r i t
y   I n f o = F a l s e ; U s e r   I D = s e l c o
; I n i t i a l   C a t a l o g = s e l c o
; D a ta   S o u r c e = S T M
In the attachment I have included the source code and the .udl. The files missing are just the LabSQL VIs.
Celso Liermann
Attachments:
Test System.zip ‏11 KB

Thank you Paolo for you advice. I fixed my bug using a simple structure.
Celso Liermann
Attachments:
Test System.zip ‏21 KB

Linking .udl file to .mdb or .accdb in programming

I`m working on the database toolkits. I can manually create an .udl file andlink to .mdb or .accdb file. Can this be done through programmatically from LabVIEW?

gnshmrthy wrote:
Hi Ranjeet,
I`m not using two different extension files i`m using either .mdl or .accdb file for an single .udl file.
Let me be more clear here I`m linking an test.udl file with the test.accdb. I can manually link the file by selecting the OLED function and specifying the path but I need to do this in program so every time when I run the program I can retrive those data if I have entered already.
The UDL is a text file, which you'll see if you open it in Notepad.
However, as suggested, it's alot easier to use 2 UDLs and choose/select between them.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

How to use a data link file (UDL)

Hi,
several times I developed applications using Crystal Reports 2008 which used a data base on my development PC and when I deployed them on a production server I had the problem to change the Data Source Location to reflect the new Server name and SQL Server Instance. Moreover, this had to be done on the server, because CR 2008 check the new data source location when you change it, and because I was not connected to the server I couldn't do it on my development pc.
I thought that the data link file was the solution to this problem, meaning that CR2008 could use a data link file (UDL file) as a data source location, so when deploying the reports on the server I had only to point the data link file to the new server instance.
With my surprise, I have seen that when using a data link file to define the data source in CR 2008, it copies the definition found in it, instead of using it at run time. SO when I deploy the reports on the server I still have the same problem to change the data source location for all the reports.
Perhaps I didn't understand the data link file use. So, how do I solve the problem of using a data source location that can be valid when deploying the reports on a server?
Thanks

Hi Antonio,
Go to our download page above, there you will find samples to test with:
http://www.sdn.sap.com/irj/boc/samples
Or to .NET samples: http://www.sdn.sap.com/irj/boc/samples?rid=/webcontent/uuid/80774579-b086-2b10-db91-ed58c4dda375 [original link is broken]
Find any of them that sets database location/log on.
Thank you
Don

Extended Analytics - Is it possible to extract data from HFM to MS Access through an UDL (OBDC) file?

Hello,
I am trying to extract data from HFM, using Extended Analytics, to MS Access through an UDL (OBDC) file but it displays the following error:
"error occurred while connecting to the database"
I've followed these steps:
1. Create a blank MS Access database (.mdb format)
2. Create an .UDL file which connects to MS Access database:
      - Provider: Microsoft Jet 4.0 OLE DB Provider
      - Connection: Linked to the .mdb database created in step 1.
      - Give "ReadWrite" permissions.
3. Test .UDL file connection successfully.
4. Create DNS with Extended Analytics DNS Configuration tool.
5. In Extended Analytics (HFM), once selected the new DNS and extract it displays the error commented before.
¿Do you know how i can solve this issue?
Thank you in advance,
Best regards,

Hello Anjum Ara,
Thank you for your response.
I don't understand how to add my database SID to tnsnames.ora. (I already found the file but i don't know how to add new database SID)
I have created one MS Access database in "C:\TEST.mdb" and i want to connect Extended Analytics to it.
How i have to add this database into tnsnames.ora file?
Thank you in advance,
Kind regards

Why can't I create UDLs?

Greetings everybody,
I'm developing an application with LV7.1 that should communicate (read/write) with Oracle Database.
Anyway, I did it succesfully using database connectivity toolset (using Universal Data Link "UDL")
So what is the problem?
The very strange problem is that when I tried to create a UDL in another machine,simply I couldn't !!!
Usually I Right-click on any area on the desktop, then click New, then select Microsoft Data Link and it's done
Now, I can't see the "Microsoft Data Link" option on the menu ?! (Please see the screen shot attatched).
Isn't this strange? And how can overcome this?!
Thanks in advance.
Ayman Mohammad Metwally
Automation Engineer
Egypt - Cairo
Attachments:
UDL.JPG ‏44 KB

Thanks tst for your reply,
Well, I just copied the UDL file form the other machine and it works well in the current machine, I can modify it also to what ever I need.
I just don't want to move to DSNs (ODBC) is that I saw many Data Base experts ( from other VB forums) saying that using OLE DB (Which uses UDLs) is better that ODBC (which uses DSNs). They said that it's faster and more efficient.
I really don't have a problem now (by coping the UDL and maybe later I'll include it in my exe package) but I wanted to know why I can't create new ones from the scratch. Well, as you said, a Windows's feature.
Thanks again for reply
Ayman Mohammad Metwally
Automation Engineer
Egypt - Cairo

How to open an external file in Labview?

Hi, Who knows how to open an external file in LabView? I want to open an .UDL file(data link API) which is a dialog window letting me input correlated database information, but I dont know how to open this type of file in my LabView Program.
Thanks.
Red

A UDL is technically a text file, so you could open it with "Read Characters from file", put the result string into a string control, edit it and save it back using the "Write Characters to File".
UDLs however have their own configuration dialog embedded in the Windows OS. You can use this dialog in your LabVIEW application. The attached VI shows how to create a new UDL. You can edit an existing UDL by switching the method node to PromptEdit and wiring in an open ADO connection reference.
Attachments:
ConfigureDatabaseConnection.vi ‏26 KB

Database udl

Hello,
I have created a vi for accessing a udl file and put the data from the file to a table in front panel. but unfortunately when i run it its giving an error.
Error:
NI_Database_API.lvlibB Tools Open Connec (String).vi->NI_Database_API.lvlibB Tools Open Connec (Path).vi->TutorialGenerateDisplay 1.vi<ERR>ADO Error: 0x800300FB
Exception occured in Microsoft OLE DB Service Components: The file is not a valid compound file. in NI_Database_API.lvlibB Tools Open Connec (String).vi->NI_Database_API.lvlibB Tools Open Connec (Path).vi->TutorialGenerateDisplay 1.vi"
I have attached the block diagram..Is that the right way to acess database.
Thanking you,
Sushmith
Attachments:
db.JPG ‏86 KB

The error you reported indicates that the wrong provider is specified in the UDL file.
http://digital.ni.com/public.nsf/websearch/1D5EB4DCBD13106486256B9D005E11B0?OpenDocument
http://digital.ni.com/public.nsf/allkb/5351D6732E4100B586256F700060CC17?OpenDocument
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

Read access mdb file in labview via ADO/DAO problem

Hi guys,
I am now facing one problem that I want to import ACCESS database (ver2000) files into labview and turn it into tables.
but if I use ADO(actually using LABSQL) I have to create the ODBC in control panel, if I use DAO, I don't know how to call the activeX method.
I would like to realize like this:
choose in a directory which mdb file I would like to open, and then open it and show it in a labview table, but using AD0 I have to create connection for each file, does it stand a chance to open it without specify the connection in control panel?
He Liang

You can use a Connection String defined by you like this
You can get the basic connection string by creating a UDL file and editing that file in Wordpad.
Hope this helps
David
Message Edited by David Crawford on 11-27-2006 01:04 PM
Attachments:
Connection String.jpg ‏13 KB

I want to access the database with user name and password without con. info/udl

hi to all,
im doing project related with database... normally i'll connect ***.udl file to open database.vi.
now what is my question is I want to open the database with the user name with password.... y i need this because once i run the program the program should ask username and password to open database for write/read operation. if its wrong user name and password means program should be denied...
can any tell how to access the database toolkit with the username with password....
im using labview 7.0...
i think my question is clear....waiting for reply thank you in advance...
pls see this attachment.....
Regards,
N. Srinivasan
Attachments:
access.vi ‏37 KB

i have already read that link in the discussion forum...but im still have some confussion in... i attached file is so like to give user name and password..?
and one more things can tell wat to do in ODBC and MDB and in UDL for password lock.. each time i run the promgram it should ask password to acces the database..
thank you a lot for your reply..
it will be more more useful if u clear my doubts clearly....
Regards,
N. Srinivasan
Attachments:
user=pass.PNG ‏35 KB

CallManager 4.2 ... UDL file

Similar Messages

Maybe you are looking for