Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

winCC call VBA macro

Created by: ranr_mids at: 12/5/2005 5:51 PM (12 Replies)

Rating (6)

Thanks 0

Result pages:: |; 1 | 2; |

13 Entries

Entries per page: 10 | all

12/5/2005 5:51 PM	Rate (0)
ranr_mids Bronze Member Joined: 12/5/2005 Last visit: 8/9/2021 Posts: 289 Rating: (19)	Hello I am trying to open a window in winCC V6.0 to display a text file which can be edited and saved and reopened etc. I do not just want to open Notepad asi do not want any of the menus available. I have done this in VBA which calls a form with a input text box which writes to a notepad file. I cannottranslate this to VBS and neither can i call thevba macro from runtime? I dont think this is possible anyway? Can anyone help Thanks

Suggestion To thank Quote Answer

12/6/2005 1:18 PM	Rate (0)
Salma Gold Member Joined: 9/27/2005 Last visit: 11/27/2007 Posts: 1398 Rating: (151)	Anything is possible in WinCC [:)] Could you post your VBA code here? Also what text box are you using? The MS Forms 2.0 one or another? Regards, Salma

Suggestion To thank Quote Answer

12/7/2005 10:24 AM	Rate (0)
ranr_mids Bronze Member Joined: 12/5/2005 Last visit: 8/9/2021 Posts: 289 Rating: (19)	Hello Salma Heres the VBA code i used. The Text box used is the Textbox on the VB form Toolbox? Thanks Jim Option Explicit Dim savPath As String Private Sub cmdText1_Click() Call TxtLoad("C:\Work\sample1.txt") savPath = "C:\Work\sample1.txt" End Sub 'Private Sub cmdText2_Click() 'Call TxtLoad("C:\Work\sample3.txt") 'savPath = "C:\Work\sample3.txt" 'End Sub Private Sub TxtLoad(Path) Dim ContentsOfFile As String Dim SizeOfFile As Integer Dim FileNumber As Integer Dim PathName As String PathName = Path FileNumber = FreeFile Open PathName For Input Access Read As FileNumber 'Find the size of the open file using LOF function SizeOfFile = LOF(FileNumber) ContentsOfFile = Input(SizeOfFile, FileNumber) txtUserInput = ContentsOfFile Close #FileNumber End Sub Private Sub cmdSaveToFile_Click() Dim FileNumber As Integer Dim PathName As String Dim TextToSave As String PathName = savPath FileNumber = FreeFile TextToSave = txtUserInput.Text Open PathName For Output Access Write As #FileNumber Print #FileNumber, TextToSave Close #FileNumber End Sub Private Sub cmdExit_Click() Form1.Hide End Sub

Suggestion To thank Quote Answer

12/8/2005 10:02 AM	Rate (2)
Salma Gold Member Joined: 9/27/2005 Last visit: 11/27/2007 Posts: 1398 Rating: (151)	Sorry for the delay in replying. Instead of the VB text box I used the Microsoft Rich Text Box Control. This allows the user to type in free form text and you can save it to a file using the following script on a button: [code] Dim txtbox Set txtbox = ScreenItems("Control1") txtbox.SaveFile "C:\test.txt", 1 ' 1 = ASCII 0 = Rich Text [/code] Try this and let us know if it does what you need. Regards, Salma

Suggestion To thank Quote Answer

12/8/2005 1:03 PM	Rate (1)
ranr_mids Bronze Member Joined: 12/5/2005 Last visit: 8/9/2021 Posts: 289 Rating: (19)	Hi Salma Your 3 lines ofscript work better than my whole page. It works just as i want it to Thanks for your help

Suggestion To thank Quote Answer

1/23/2006 12:57 PM	Rate (0)
ranr_mids Bronze Member Joined: 12/5/2005 Last visit: 8/9/2021 Posts: 289 Rating: (19)	Greetings. I have discovered a problem relating to OCX controls, while transferring my project to the destination machine. All my text box controls were configured to use the Microsoft RichText OCX Control, while using WinCC V6.0.2.0 on Windows 2000. The 'end user' machines run WinCC V6.0.3.0 on Server 2003 (server)or XP (clients). All of them generate an error message when trying to use the above OCX (even though the file name, version and size are identical). The error says "License Information not found. You do not possess a valid license for the design mode. (RichtextCtrl)" Which license is it referring to, and why was it perfectly happy to use this OCX on the original development machine?

Suggestion To thank Quote Answer

1/23/2006 3:02 PM	Rate (1)
Reuben Posts: 70 Rating: (13)	Hi I don't have exact information at hand but I have had similar issues, depending on which OCX controls are used. On my development machine I may have something like MS Office installed that actually includes design licenses for certain MS OCX controls, meaning you are allowed to edit properties and such in design mode like in VB, Delphior WinCC Graphics Designer. The target machine, which is a "bare minimum" machine, may not have such licensed versions installed. If you try to edit it on the target machine you get the error - but it should still work OK in Runtime, you just cannot edit the control with Graphics Designer. Reuben
Reuben Posts: 70 Rating: (13)
Suggestion To thank Quote Answer

1/23/2006 5:11 PM	Rate (0)
ranr_mids Bronze Member Joined: 12/5/2005 Last visit: 8/9/2021 Posts: 289 Rating: (19)	Reuben, thank you for your insight into this problem. I was not aware such 'hidden' MS licensing went on, especially with components that are available within the basic operating system. The control in question does not function in Runtime, and my problem is compounded by the different operating systems - the OCX I am trying to use is stored in a different location on my development machine than on all the 'end user' machines. I have tried copying the file into the place it is expected and re-registering it, but still get the errors.

Suggestion To thank Quote Answer

1/24/2006 9:05 AM	Rate (0)
Ikkezelf Posts: 1084 Rating: (72)	Just an Idea, Open the graphic designer on the machine where you want to run the ocx on. Open the Visual Basic Editor <Alt> + <F11> Go to Tools -> references and check the checkbos in front of the references you are using. Press OK, then close and try if it works now. Not sure if it works, but you can test it very fast. with regards
Ikkezelf Posts: 1084 Rating: (72)
Suggestion To thank Quote Answer

1/30/2006 9:27 AM	Rate (0)
ranr_mids Bronze Member Joined: 12/5/2005 Last visit: 8/9/2021 Posts: 289 Rating: (19)	The OCX I am using (the Microsoft Richtext box) does not seem to be on the Visual Basic Editor's list - unless I am missing something obvious. Can someone suggest an alternative that will work under Windows Server 2003 (Standard) and XP Pro?

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on