BillCharlton
Programmer
Has anyone ever come across a specification that describes the format and layout of Visual basic files that contain
source code (e.g., .frm, .cls) files?
source code (e.g., .frm, .cls) files?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
specification for VB files containing source code
- Thread starter BillCharlton
- Start date
- Status
MichaelRed
Programmer
Hmmmmmmmmmmmm,
No formal specification,
BUT
It is 'easy' to look at these if you a 'stout of heart'.
Open Wordpad (notepad is Also O.K. - most of the time). Navvigate to the desired object throught eh file open dialog. Open thec file. Everthing in all of VB (Source) is stored as plain text. It is just that VB 'registers' the extensions as VB objects, so when you "open" one of them from explorer et. al., it launches VB to open the file.
You will - in general see some "header" information, followed by the code modules. For the forms - in particular - you will recognise the various controls (name and attributes).
Class andf module files have some (but MUCH less) header info. All of it more-or-less makes sense, although a few lines can/will cause trouble if they are changed improperly.
MichaelRed
redmsp@erols.com
There is never time to do it right but there is always time to do it over
No formal specification,
BUT
It is 'easy' to look at these if you a 'stout of heart'.
Open Wordpad (notepad is Also O.K. - most of the time). Navvigate to the desired object throught eh file open dialog. Open thec file. Everthing in all of VB (Source) is stored as plain text. It is just that VB 'registers' the extensions as VB objects, so when you "open" one of them from explorer et. al., it launches VB to open the file.
You will - in general see some "header" information, followed by the code modules. For the forms - in particular - you will recognise the various controls (name and attributes).
Class andf module files have some (but MUCH less) header info. All of it more-or-less makes sense, although a few lines can/will cause trouble if they are changed improperly.
MichaelRed
redmsp@erols.com
There is never time to do it right but there is always time to do it over
- Status
Similar threads
- Question