
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Visual Cobol indentation reset using Visual Studio 2019
We are using Visual Studio Personal Edition with Visual Studio 2019. When entering a program with indentation, the indentation is removed when you reload the program. Any suggestions? I'm using it to teach Cobol and don't wish to switch platforms but need the indentation.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Can you please provide more detail on exactly what it is that you are experiencing?
What do you mean by indentation? Are you using tabs to align source elements and then when you save and reload the programs these tabs are missing?
Showing us a screenshot of the indentation before and after would be helpful...

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi @Wilson87
Could you provide us with the current version of Visual Studio 2019 and Visual COBOL you are using. For example:
Visual Studio 16.7.7
Visual COBOL 6.0 HF 1

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Here are the versions of Visual Studio and MicroFocus we are using:
Visual Studio Community 2019 - Version 16.7.4
Micro Focus Visual Cobol 5.0
Micro Focus IMTK Client Generator 1.0

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
I have attached a screen shot of the students software versions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
I think you might be hitting a regression introduced by a VS 2019 update. The fix for this is available in the latest patch update for Visual COBOL 5.0 and 6.0. You can view more information and a potential workaround here: