[Migrated content. Thread originally posted on 25 March 2011]

We are very new at the .net world but have purchased Visual Cobol because it can access our current vision file data without converting the data (so we understand).

Our first issue is that we can't seem to find a way to get a project to see our current vision data files. Can someone please send me some pointers/clues/hints on how you get a new project to see a vision data file.

Thanks for ANY help.

TonyLeBlanc originally wrote:
Continuing our testing/learning of VC using Vision files - we have a Vision file that was created with compression, but VC doesn't like the SELECT statement:
SELECT ORDER-FILE
ASSIGN TO RANDOM , "OMORD.DAT"
WITH COMPRESSION
COMPRESSION IS 100
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
LOCK MODE IS MANUAL
RECORD KEY IS ORD-INV-NUM-KEY
ALTERNATE RECORD KEY IS ORD-ACCOUNT-JOB-KEY
etc

The "COMPRESSION IS 100" statement is being rejected by VC. Are there options with Vision files that aren't supported by the VC Vision file handler, or am I missing something?

Tony,

Since MF COBOL rejects the compression setting in the select, you should still be able to put this in your A_CONFIG file:

COMPRESS_FACTOR 100

I may be slightly off, but don't think so. Look in the Acu manuals appendices that cover configuration variables. See both COMPRESS_FACTOR and COMPRESS_FILES.

I think you'll be able to get exactly what you want. It's just like ACUCOBOL-GT to give you both ways to do it: the SELECT or the CONFIG file.

Let me know if that helps.

Thanks,

Dan

---

[Migrated content. Thread originally posted on 25 March 2011]

We are very new at the .net world but have purchased Visual Cobol because it can access our current vision file data without converting the data (so we understand).

Our first issue is that we can't seem to find a way to get a project to see our current vision data files. Can someone please send me some pointers/clues/hints on how you get a new project to see a vision data file.

Thanks for ANY help.

TonyLeBlanc originally wrote:
Continuing our testing/learning of VC using Vision files - we have a Vision file that was created with compression, but VC doesn't like the SELECT statement:
SELECT ORDER-FILE
ASSIGN TO RANDOM , "OMORD.DAT"
WITH COMPRESSION
COMPRESSION IS 100
ORGANIZATION IS INDEXED
ACCESS MODE IS DYNAMIC
LOCK MODE IS MANUAL
RECORD KEY IS ORD-INV-NUM-KEY
ALTERNATE RECORD KEY IS ORD-ACCOUNT-JOB-KEY
etc

The "COMPRESSION IS 100" statement is being rejected by VC. Are there options with Vision files that aren't supported by the VC Vision file handler, or am I missing something?

Tony,

Since MF COBOL rejects the compression setting in the select, you should still be able to put this in your A_CONFIG file:

COMPRESS_FACTOR 100

I may be slightly off, but don't think so. Look in the Acu manuals appendices that cover configuration variables. See both COMPRESS_FACTOR and COMPRESS_FILES.

I think you'll be able to get exactly what you want. It's just like ACUCOBOL-GT to give you both ways to do it: the SELECT or the CONFIG file.

Let me know if that helps.

Thanks,

Dan

---