Trimble Business Center

Hopefully, someone can help with this;
I have been using codes and linework commands for  quite awhile, but I've been using Survey Pro for the vast majority of time.  I have an .FXL file that contains linework codes and feature definition codes already (and loaded properly on my TSC7).  

I've now started implementing Access for my boundary and topo type work, though.  Everything seems okay, but when I started adding to my groups for Measure Codes (i.e., 5x5, 4x5...) Access doesn't seem to like the way I've entered my codes.  I've entered my codes like this:

132 B (132 is EP and B is Begin)
132
132 E (E is End)
132 CLS (CLS is Close)
…and so on.

When I try to take a shot using this method, Access has a window that pops up and says, "Error-132 B does not contain any line features"

I've gone back to my .fxl and verified that it is properly input and it is.  This is the same feature code file I've used for many years.

My assumption would be that the CAD toolbar is having some effect on my code input?  

Ultimately, I don't care how Access deals with my codes/linework commands, though (at least I don't THINK I care).  I process all my data using Civil 3d - which has worked perfectly for me for many years.  I merely want my points to be measured the way I have them input, so I can export an ASCII file upon completion of fieldwork and import that directly into C3D.

------------------------------
MP (NV)
------------------------------

Hey Mark, 

Is it possible to provide the FXL file for review?

Regards,

Shane Lyons
Trimble Support

------------------------------
Shane Lyons
------------------------------

Original Message:
Sent: 02-23-2021 07:08
From: mark Prewitt
Subject: Access Linework Codes Error

Hopefully, someone can help with this;
I have been using codes and linework commands for  quite awhile, but I've been using Survey Pro for the vast majority of time.  I have an .FXL file that contains linework codes and feature definition codes already (and loaded properly on my TSC7).  

I've now started implementing Access for my boundary and topo type work, though.  Everything seems okay, but when I started adding to my groups for Measure Codes (i.e., 5x5, 4x5...) Access doesn't seem to like the way I've entered my codes.  I've entered my codes like this:

132 B (132 is EP and B is Begin)
132
132 E (E is End)
132 CLS (CLS is Close)
…and so on.

When I try to take a shot using this method, Access has a window that pops up and says, "Error-132 B does not contain any line features"

I've gone back to my .fxl and verified that it is properly input and it is.  This is the same feature code file I've used for many years.

My assumption would be that the CAD toolbar is having some effect on my code input?  

Ultimately, I don't care how Access deals with my codes/linework commands, though (at least I don't THINK I care).  I process all my data using Civil 3d - which has worked perfectly for me for many years.  I merely want my points to be measured the way I have them input, so I can export an ASCII file upon completion of fieldwork and import that directly into C3D.

------------------------------
MP (NV)
------------------------------

Shane, 
For whatever reason, I cant seem to upload a file.  Can I email it to you?

------------------------------
mark Prewitt
------------------------------

Original Message:
Sent: 02-23-2021 09:04
From: Shane Lyons
Subject: Access Linework Codes Error

Hey Mark, 

Is it possible to provide the FXL file for review?

Regards,

Shane Lyons
Trimble Support

------------------------------
Shane Lyons

Original Message:
Sent: 02-23-2021 07:08
From: mark Prewitt
Subject: Access Linework Codes Error

Hopefully, someone can help with this;
I have been using codes and linework commands for  quite awhile, but I've been using Survey Pro for the vast majority of time.  I have an .FXL file that contains linework codes and feature definition codes already (and loaded properly on my TSC7).  

I've now started implementing Access for my boundary and topo type work, though.  Everything seems okay, but when I started adding to my groups for Measure Codes (i.e., 5x5, 4x5...) Access doesn't seem to like the way I've entered my codes.  I've entered my codes like this:

132 B (132 is EP and B is Begin)
132
132 E (E is End)
132 CLS (CLS is Close)
…and so on.

When I try to take a shot using this method, Access has a window that pops up and says, "Error-132 B does not contain any line features"

I've gone back to my .fxl and verified that it is properly input and it is.  This is the same feature code file I've used for many years.

My assumption would be that the CAD toolbar is having some effect on my code input?  

Ultimately, I don't care how Access deals with my codes/linework commands, though (at least I don't THINK I care).  I process all my data using Civil 3d - which has worked perfectly for me for many years.  I merely want my points to be measured the way I have them input, so I can export an ASCII file upon completion of fieldwork and import that directly into C3D.

------------------------------
MP (NV)
------------------------------

Here you go, Shane.

Let me know if this is totally screwed up.  :)

------------------------------
mark Prewitt
------------------------------

Original Message:
Sent: 02-23-2021 09:04
From: Shane Lyons
Subject: Access Linework Codes Error

Hey Mark, 

Is it possible to provide the FXL file for review?

Regards,

Shane Lyons
Trimble Support

------------------------------
Shane Lyons

Original Message:
Sent: 02-23-2021 07:08
From: mark Prewitt
Subject: Access Linework Codes Error

Hopefully, someone can help with this;
I have been using codes and linework commands for  quite awhile, but I've been using Survey Pro for the vast majority of time.  I have an .FXL file that contains linework codes and feature definition codes already (and loaded properly on my TSC7).  

I've now started implementing Access for my boundary and topo type work, though.  Everything seems okay, but when I started adding to my groups for Measure Codes (i.e., 5x5, 4x5...) Access doesn't seem to like the way I've entered my codes.  I've entered my codes like this:

132 B (132 is EP and B is Begin)
132
132 E (E is End)
132 CLS (CLS is Close)
…and so on.

When I try to take a shot using this method, Access has a window that pops up and says, "Error-132 B does not contain any line features"

I've gone back to my .fxl and verified that it is properly input and it is.  This is the same feature code file I've used for many years.

My assumption would be that the CAD toolbar is having some effect on my code input?  

Ultimately, I don't care how Access deals with my codes/linework commands, though (at least I don't THINK I care).  I process all my data using Civil 3d - which has worked perfectly for me for many years.  I merely want my points to be measured the way I have them input, so I can export an ASCII file upon completion of fieldwork and import that directly into C3D.

------------------------------
MP (NV)
------------------------------

Thanks Mark. 

I've got some meetings this morning but will get this downloaded and let you know what I find ASAP. 

Regards,

Shane Lyons
Trimble Support


------------------------------
Shane Lyons
------------------------------

Original Message:
Sent: 02-24-2021 07:16
From: mark Prewitt
Subject: Access Linework Codes Error

Here you go, Shane.

Let me know if this is totally screwed up.  :)

------------------------------
mark Prewitt

Original Message:
Sent: 02-23-2021 09:04
From: Shane Lyons
Subject: Access Linework Codes Error

Hey Mark, 

Is it possible to provide the FXL file for review?

Regards,

Shane Lyons
Trimble Support

------------------------------
Shane Lyons

Original Message:
Sent: 02-23-2021 07:08
From: mark Prewitt
Subject: Access Linework Codes Error

Hopefully, someone can help with this;
I have been using codes and linework commands for  quite awhile, but I've been using Survey Pro for the vast majority of time.  I have an .FXL file that contains linework codes and feature definition codes already (and loaded properly on my TSC7).  

I've now started implementing Access for my boundary and topo type work, though.  Everything seems okay, but when I started adding to my groups for Measure Codes (i.e., 5x5, 4x5...) Access doesn't seem to like the way I've entered my codes.  I've entered my codes like this:

132 B (132 is EP and B is Begin)
132
132 E (E is End)
132 CLS (CLS is Close)
…and so on.

When I try to take a shot using this method, Access has a window that pops up and says, "Error-132 B does not contain any line features"

I've gone back to my .fxl and verified that it is properly input and it is.  This is the same feature code file I've used for many years.

My assumption would be that the CAD toolbar is having some effect on my code input?  

Ultimately, I don't care how Access deals with my codes/linework commands, though (at least I don't THINK I care).  I process all my data using Civil 3d - which has worked perfectly for me for many years.  I merely want my points to be measured the way I have them input, so I can export an ASCII file upon completion of fieldwork and import that directly into C3D.

------------------------------
MP (NV)
------------------------------

Hey Mark, 

The FXL that was sent contains no line features, only point features. 

You said when you opened in FDM everything looked correct. Are you not seeing this on your end? 

I had our Survey Pro team look at it as well and they are seeing the same thing. Is there another FXL that contains the line features? 

Regards,

Shane Lyons
Trimble Support

------------------------------
Shane Lyons
------------------------------

Original Message:
Sent: 02-24-2021 07:16
From: mark Prewitt
Subject: Access Linework Codes Error

Here you go, Shane.

Let me know if this is totally screwed up.  :)

------------------------------
mark Prewitt

Original Message:
Sent: 02-23-2021 09:04
From: Shane Lyons
Subject: Access Linework Codes Error

Hey Mark, 

Is it possible to provide the FXL file for review?

Regards,

Shane Lyons
Trimble Support

------------------------------
Shane Lyons

Original Message:
Sent: 02-23-2021 07:08
From: mark Prewitt
Subject: Access Linework Codes Error

Hopefully, someone can help with this;
I have been using codes and linework commands for  quite awhile, but I've been using Survey Pro for the vast majority of time.  I have an .FXL file that contains linework codes and feature definition codes already (and loaded properly on my TSC7).  

I've now started implementing Access for my boundary and topo type work, though.  Everything seems okay, but when I started adding to my groups for Measure Codes (i.e., 5x5, 4x5...) Access doesn't seem to like the way I've entered my codes.  I've entered my codes like this:

132 B (132 is EP and B is Begin)
132
132 E (E is End)
132 CLS (CLS is Close)
…and so on.

When I try to take a shot using this method, Access has a window that pops up and says, "Error-132 B does not contain any line features"

I've gone back to my .fxl and verified that it is properly input and it is.  This is the same feature code file I've used for many years.

My assumption would be that the CAD toolbar is having some effect on my code input?  

Ultimately, I don't care how Access deals with my codes/linework commands, though (at least I don't THINK I care).  I process all my data using Civil 3d - which has worked perfectly for me for many years.  I merely want my points to be measured the way I have them input, so I can export an ASCII file upon completion of fieldwork and import that directly into C3D.

------------------------------
MP (NV)
------------------------------

Sorry, for not responding sooner.  I was in the field.

I think that my understanding of how Access is using codes isn't correct.  

I (for years) have been simply associating my .fxl with my Survey Pro jobs and merely using codes and linework codes for my work; however, I have not been using it to produce auto-linework within the data collector.  Again, I process all my linework in C3D, so I haven't had much use for it in my DC.  I can definitely see the benefit from it, though.  Seeing your linework as its shot can have great benefit, for sure.

When you said, "The FXL that was sent contains no line features, only point features." I didn't understand that.  I'm thinking to myself, I've been using linework codes for years, but looking a bit deeper into the line features within the Definition Manager, I now see exactly what you're talking about.  This will definitely take some time to update, but not impossible.  

I appreciate your response and assistance.  It opened my eyes to a new feature that I've never dealt with before.

That said, can I not simply shoot codes using my LINE CONTROL CODES (only), as I've done for so long and just simply export a .txt (ASCII) file upon completion?  That way, until I update my .fxl file with new Line Feature Definitions, I can continue getting what I need...  Doesn't appear that's possible.





------------------------------
mark Prewitt
------------------------------

Original Message:
Sent: 02-24-2021 13:29
From: Shane Lyons
Subject: Access Linework Codes Error

Hey Mark, 

The FXL that was sent contains no line features, only point features. 

You said when you opened in FDM everything looked correct. Are you not seeing this on your end? 

I had our Survey Pro team look at it as well and they are seeing the same thing. Is there another FXL that contains the line features? 

Regards,

Shane Lyons
Trimble Support

------------------------------
Shane Lyons

Original Message:
Sent: 02-24-2021 07:16
From: mark Prewitt
Subject: Access Linework Codes Error

Here you go, Shane.

Let me know if this is totally screwed up.  :)

------------------------------
mark Prewitt

Original Message:
Sent: 02-23-2021 09:04
From: Shane Lyons
Subject: Access Linework Codes Error

Hey Mark, 

Is it possible to provide the FXL file for review?

Regards,

Shane Lyons
Trimble Support

------------------------------
Shane Lyons

Original Message:
Sent: 02-23-2021 07:08
From: mark Prewitt
Subject: Access Linework Codes Error

Hopefully, someone can help with this;
I have been using codes and linework commands for  quite awhile, but I've been using Survey Pro for the vast majority of time.  I have an .FXL file that contains linework codes and feature definition codes already (and loaded properly on my TSC7).  

I've now started implementing Access for my boundary and topo type work, though.  Everything seems okay, but when I started adding to my groups for Measure Codes (i.e., 5x5, 4x5...) Access doesn't seem to like the way I've entered my codes.  I've entered my codes like this:

132 B (132 is EP and B is Begin)
132
132 E (E is End)
132 CLS (CLS is Close)
…and so on.

When I try to take a shot using this method, Access has a window that pops up and says, "Error-132 B does not contain any line features"

I've gone back to my .fxl and verified that it is properly input and it is.  This is the same feature code file I've used for many years.

My assumption would be that the CAD toolbar is having some effect on my code input?  

Ultimately, I don't care how Access deals with my codes/linework commands, though (at least I don't THINK I care).  I process all my data using Civil 3d - which has worked perfectly for me for many years.  I merely want my points to be measured the way I have them input, so I can export an ASCII file upon completion of fieldwork and import that directly into C3D.

------------------------------
MP (NV)
------------------------------

Hey Mark, 

You can still use the fxl and work as normal, you just can't use the line control features inside of measure codes. You can still enter the "B", etc, but would have to enter it manually after the code. You can't have one of the code squares be 132 B, it can only be 132. I've attached a video of how you would have to do this. 

You can also work as normal in measure points. 

let me know if you have any other questions. 

Regards,

Shane Lyons
Trimble Support



------------------------------
Shane Lyons
------------------------------

Original Message:
Sent: 02-25-2021 07:09
From: mark Prewitt
Subject: Access Linework Codes Error

Sorry, for not responding sooner.  I was in the field.

I think that my understanding of how Access is using codes isn't correct.  

I (for years) have been simply associating my .fxl with my Survey Pro jobs and merely using codes and linework codes for my work; however, I have not been using it to produce auto-linework within the data collector.  Again, I process all my linework in C3D, so I haven't had much use for it in my DC.  I can definitely see the benefit from it, though.  Seeing your linework as its shot can have great benefit, for sure.

When you said, "The FXL that was sent contains no line features, only point features." I didn't understand that.  I'm thinking to myself, I've been using linework codes for years, but looking a bit deeper into the line features within the Definition Manager, I now see exactly what you're talking about.  This will definitely take some time to update, but not impossible.  

I appreciate your response and assistance.  It opened my eyes to a new feature that I've never dealt with before.

That said, can I not simply shoot codes using my LINE CONTROL CODES (only), as I've done for so long and just simply export a .txt (ASCII) file upon completion?  That way, until I update my .fxl file with new Line Feature Definitions, I can continue getting what I need...  Doesn't appear that's possible.





------------------------------
mark Prewitt

Original Message:
Sent: 02-24-2021 13:29
From: Shane Lyons
Subject: Access Linework Codes Error

Hey Mark, 

The FXL that was sent contains no line features, only point features. 

You said when you opened in FDM everything looked correct. Are you not seeing this on your end? 

I had our Survey Pro team look at it as well and they are seeing the same thing. Is there another FXL that contains the line features? 

Regards,

Shane Lyons
Trimble Support

------------------------------
Shane Lyons

Original Message:
Sent: 02-24-2021 07:16
From: mark Prewitt
Subject: Access Linework Codes Error

Here you go, Shane.

Let me know if this is totally screwed up.  :)

------------------------------
mark Prewitt

Original Message:
Sent: 02-23-2021 09:04
From: Shane Lyons
Subject: Access Linework Codes Error

Hey Mark, 

Is it possible to provide the FXL file for review?

Regards,

Shane Lyons
Trimble Support

------------------------------
Shane Lyons

Original Message:
Sent: 02-23-2021 07:08
From: mark Prewitt
Subject: Access Linework Codes Error

Hopefully, someone can help with this;
I have been using codes and linework commands for  quite awhile, but I've been using Survey Pro for the vast majority of time.  I have an .FXL file that contains linework codes and feature definition codes already (and loaded properly on my TSC7).  

I've now started implementing Access for my boundary and topo type work, though.  Everything seems okay, but when I started adding to my groups for Measure Codes (i.e., 5x5, 4x5...) Access doesn't seem to like the way I've entered my codes.  I've entered my codes like this:

132 B (132 is EP and B is Begin)
132
132 E (E is End)
132 CLS (CLS is Close)
…and so on.

When I try to take a shot using this method, Access has a window that pops up and says, "Error-132 B does not contain any line features"

I've gone back to my .fxl and verified that it is properly input and it is.  This is the same feature code file I've used for many years.

My assumption would be that the CAD toolbar is having some effect on my code input?  

Ultimately, I don't care how Access deals with my codes/linework commands, though (at least I don't THINK I care).  I process all my data using Civil 3d - which has worked perfectly for me for many years.  I merely want my points to be measured the way I have them input, so I can export an ASCII file upon completion of fieldwork and import that directly into C3D.

------------------------------
MP (NV)
------------------------------

Understood.  That would be fairly cumbersome to have to add it manually.

So, to be clear I simply need to update my .FXL to incorporate line feature definitions, then Access will be able to process the code, linework code and line feature definition at once.  Then (and only then) I will be able to have code squares like 132 B, 132 E etc?

------------------------------
mark Prewitt
------------------------------

Original Message:
Sent: 02-25-2021 07:52
From: Shane Lyons
Subject: Access Linework Codes Error

Hey Mark, 

You can still use the fxl and work as normal, you just can't use the line control features inside of measure codes. You can still enter the "B", etc, but would have to enter it manually after the code. You can't have one of the code squares be 132 B, it can only be 132. I've attached a video of how you would have to do this. 

You can also work as normal in measure points. 

let me know if you have any other questions. 

Regards,

Shane Lyons
Trimble Support



------------------------------
Shane Lyons

Original Message:
Sent: 02-25-2021 07:09
From: mark Prewitt
Subject: Access Linework Codes Error

Sorry, for not responding sooner.  I was in the field.

I think that my understanding of how Access is using codes isn't correct.  

I (for years) have been simply associating my .fxl with my Survey Pro jobs and merely using codes and linework codes for my work; however, I have not been using it to produce auto-linework within the data collector.  Again, I process all my linework in C3D, so I haven't had much use for it in my DC.  I can definitely see the benefit from it, though.  Seeing your linework as its shot can have great benefit, for sure.

When you said, "The FXL that was sent contains no line features, only point features." I didn't understand that.  I'm thinking to myself, I've been using linework codes for years, but looking a bit deeper into the line features within the Definition Manager, I now see exactly what you're talking about.  This will definitely take some time to update, but not impossible.  

I appreciate your response and assistance.  It opened my eyes to a new feature that I've never dealt with before.

That said, can I not simply shoot codes using my LINE CONTROL CODES (only), as I've done for so long and just simply export a .txt (ASCII) file upon completion?  That way, until I update my .fxl file with new Line Feature Definitions, I can continue getting what I need...  Doesn't appear that's possible.





------------------------------
mark Prewitt

Original Message:
Sent: 02-24-2021 13:29
From: Shane Lyons
Subject: Access Linework Codes Error

Hey Mark, 

The FXL that was sent contains no line features, only point features. 

You said when you opened in FDM everything looked correct. Are you not seeing this on your end? 

I had our Survey Pro team look at it as well and they are seeing the same thing. Is there another FXL that contains the line features? 

Regards,

Shane Lyons
Trimble Support

------------------------------
Shane Lyons

Original Message:
Sent: 02-24-2021 07:16
From: mark Prewitt
Subject: Access Linework Codes Error

Here you go, Shane.

Let me know if this is totally screwed up.  :)

------------------------------
mark Prewitt

Original Message:
Sent: 02-23-2021 09:04
From: Shane Lyons
Subject: Access Linework Codes Error

Hey Mark, 

Is it possible to provide the FXL file for review?

Regards,

Shane Lyons
Trimble Support

------------------------------
Shane Lyons

Original Message:
Sent: 02-23-2021 07:08
From: mark Prewitt
Subject: Access Linework Codes Error

Hopefully, someone can help with this;
I have been using codes and linework commands for  quite awhile, but I've been using Survey Pro for the vast majority of time.  I have an .FXL file that contains linework codes and feature definition codes already (and loaded properly on my TSC7).  

I've now started implementing Access for my boundary and topo type work, though.  Everything seems okay, but when I started adding to my groups for Measure Codes (i.e., 5x5, 4x5...) Access doesn't seem to like the way I've entered my codes.  I've entered my codes like this:

132 B (132 is EP and B is Begin)
132
132 E (E is End)
132 CLS (CLS is Close)
…and so on.

When I try to take a shot using this method, Access has a window that pops up and says, "Error-132 B does not contain any line features"

I've gone back to my .fxl and verified that it is properly input and it is.  This is the same feature code file I've used for many years.

My assumption would be that the CAD toolbar is having some effect on my code input?  

Ultimately, I don't care how Access deals with my codes/linework commands, though (at least I don't THINK I care).  I process all my data using Civil 3d - which has worked perfectly for me for many years.  I merely want my points to be measured the way I have them input, so I can export an ASCII file upon completion of fieldwork and import that directly into C3D.

------------------------------
MP (NV)
------------------------------

mark. if you are going to update your fxl i would really consider going to alpha codes. it opens up a lot of options you might not be aware of. like i mentioned before you can shoot two strings at the same time which i often use when shooting cross sections in a road surface that have an EP1 edge pavement on one side of the road and EP2 on the other. or if you are not crossing the road and you have two levels of banks on one side you can have two top strings collecting at the same time. it is a lot less walking.
you can also have two codes for one point. i used this a bunch this summer shooting creeks. i shoot one side of the creek and have code look like this: CK1 CK2 HOS 5. where HOS is the line control for horizontal offset. and you get two lines one offset by 5m. mind you this was in survey pro, but tbc handles it so i would assume access would. not sure about c3d but i should look into it.
good luck


Original Message:
Sent: 2/25/2021 10:28:00 AM
From: mark Prewitt
Subject: RE: Access Linework Codes Error

Understood.  That would be fairly cumbersome to have to add it manually.

So, to be clear I simply need to update my .FXL to incorporate line feature definitions, then Access will be able to process the code, linework code and line feature definition at once.  Then (and only then) I will be able to have code squares like 132 B, 132 E etc?

------------------------------
mark Prewitt
------------------------------

Original Message:
Sent: 02-25-2021 07:52
From: Shane Lyons
Subject: Access Linework Codes Error

Hey Mark, 

You can still use the fxl and work as normal, you just can't use the line control features inside of measure codes. You can still enter the "B", etc, but would have to enter it manually after the code. You can't have one of the code squares be 132 B, it can only be 132. I've attached a video of how you would have to do this. 

You can also work as normal in measure points. 

let me know if you have any other questions. 

Regards,

Shane Lyons
Trimble Support



------------------------------
Shane Lyons

Original Message:
Sent: 02-25-2021 07:09
From: mark Prewitt
Subject: Access Linework Codes Error

Sorry, for not responding sooner.  I was in the field.

I think that my understanding of how Access is using codes isn't correct.  

I (for years) have been simply associating my .fxl with my Survey Pro jobs and merely using codes and linework codes for my work; however, I have not been using it to produce auto-linework within the data collector.  Again, I process all my linework in C3D, so I haven't had much use for it in my DC.  I can definitely see the benefit from it, though.  Seeing your linework as its shot can have great benefit, for sure.

When you said, "The FXL that was sent contains no line features, only point features." I didn't understand that.  I'm thinking to myself, I've been using linework codes for years, but looking a bit deeper into the line features within the Definition Manager, I now see exactly what you're talking about.  This will definitely take some time to update, but not impossible.  

I appreciate your response and assistance.  It opened my eyes to a new feature that I've never dealt with before.

That said, can I not simply shoot codes using my LINE CONTROL CODES (only), as I've done for so long and just simply export a .txt (ASCII) file upon completion?  That way, until I update my .fxl file with new Line Feature Definitions, I can continue getting what I need...  Doesn't appear that's possible.





------------------------------
mark Prewitt

Original Message:
Sent: 02-24-2021 13:29
From: Shane Lyons
Subject: Access Linework Codes Error

Hey Mark, 

The FXL that was sent contains no line features, only point features. 

You said when you opened in FDM everything looked correct. Are you not seeing this on your end? 

I had our Survey Pro team look at it as well and they are seeing the same thing. Is there another FXL that contains the line features? 

Regards,

Shane Lyons
Trimble Support

------------------------------
Shane Lyons

Original Message:
Sent: 02-24-2021 07:16
From: mark Prewitt
Subject: Access Linework Codes Error

Here you go, Shane.

Let me know if this is totally screwed up.  :)

------------------------------
mark Prewitt

Original Message:
Sent: 02-23-2021 09:04
From: Shane Lyons
Subject: Access Linework Codes Error

Hey Mark, 

Is it possible to provide the FXL file for review?

Regards,

Shane Lyons
Trimble Support

------------------------------
Shane Lyons

Original Message:
Sent: 02-23-2021 07:08
From: mark Prewitt
Subject: Access Linework Codes Error

Hopefully, someone can help with this;
I have been using codes and linework commands for  quite awhile, but I've been using Survey Pro for the vast majority of time.  I have an .FXL file that contains linework codes and feature definition codes already (and loaded properly on my TSC7).  

I've now started implementing Access for my boundary and topo type work, though.  Everything seems okay, but when I started adding to my groups for Measure Codes (i.e., 5x5, 4x5...) Access doesn't seem to like the way I've entered my codes.  I've entered my codes like this:

132 B (132 is EP and B is Begin)
132
132 E (E is End)
132 CLS (CLS is Close)
…and so on.

When I try to take a shot using this method, Access has a window that pops up and says, "Error-132 B does not contain any line features"

I've gone back to my .fxl and verified that it is properly input and it is.  This is the same feature code file I've used for many years.

My assumption would be that the CAD toolbar is having some effect on my code input?  

Ultimately, I don't care how Access deals with my codes/linework commands, though (at least I don't THINK I care).  I process all my data using Civil 3d - which has worked perfectly for me for many years.  I merely want my points to be measured the way I have them input, so I can export an ASCII file upon completion of fieldwork and import that directly into C3D.

------------------------------
MP (NV)
------------------------------

Did you know that with TA and C3D, you don't need to begin a line (using default settings)?  You only need to end or close a line.  I don't know if using B is adding to your problem or not.

------------------------------
Robert Hoy
------------------------------

Original Message:
Sent: 02-23-2021 07:08
From: mark Prewitt
Subject: Access Linework Codes Error

Hopefully, someone can help with this;
I have been using codes and linework commands for  quite awhile, but I've been using Survey Pro for the vast majority of time.  I have an .FXL file that contains linework codes and feature definition codes already (and loaded properly on my TSC7).  

I've now started implementing Access for my boundary and topo type work, though.  Everything seems okay, but when I started adding to my groups for Measure Codes (i.e., 5x5, 4x5...) Access doesn't seem to like the way I've entered my codes.  I've entered my codes like this:

132 B (132 is EP and B is Begin)
132
132 E (E is End)
132 CLS (CLS is Close)
…and so on.

When I try to take a shot using this method, Access has a window that pops up and says, "Error-132 B does not contain any line features"

I've gone back to my .fxl and verified that it is properly input and it is.  This is the same feature code file I've used for many years.

My assumption would be that the CAD toolbar is having some effect on my code input?  

Ultimately, I don't care how Access deals with my codes/linework commands, though (at least I don't THINK I care).  I process all my data using Civil 3d - which has worked perfectly for me for many years.  I merely want my points to be measured the way I have them input, so I can export an ASCII file upon completion of fieldwork and import that directly into C3D.

------------------------------
MP (NV)
------------------------------

I didn't know that.  Hmm. 

No matter what code I use, it gives the same error, though.

------------------------------
mark Prewitt
------------------------------

Original Message:
Sent: 02-23-2021 09:37
From: Robert Hoy
Subject: Access Linework Codes Error

Did you know that with TA and C3D, you don't need to begin a line (using default settings)?  You only need to end or close a line.  I don't know if using B is adding to your problem or not.

------------------------------
Robert Hoy

Original Message:
Sent: 02-23-2021 07:08
From: mark Prewitt
Subject: Access Linework Codes Error

Hopefully, someone can help with this;
I have been using codes and linework commands for  quite awhile, but I've been using Survey Pro for the vast majority of time.  I have an .FXL file that contains linework codes and feature definition codes already (and loaded properly on my TSC7).  

I've now started implementing Access for my boundary and topo type work, though.  Everything seems okay, but when I started adding to my groups for Measure Codes (i.e., 5x5, 4x5...) Access doesn't seem to like the way I've entered my codes.  I've entered my codes like this:

132 B (132 is EP and B is Begin)
132
132 E (E is End)
132 CLS (CLS is Close)
…and so on.

When I try to take a shot using this method, Access has a window that pops up and says, "Error-132 B does not contain any line features"

I've gone back to my .fxl and verified that it is properly input and it is.  This is the same feature code file I've used for many years.

My assumption would be that the CAD toolbar is having some effect on my code input?  

Ultimately, I don't care how Access deals with my codes/linework commands, though (at least I don't THINK I care).  I process all my data using Civil 3d - which has worked perfectly for me for many years.  I merely want my points to be measured the way I have them input, so I can export an ASCII file upon completion of fieldwork and import that directly into C3D.

------------------------------
MP (NV)
------------------------------

You should be able to upload a file to here, you'll just have to ZIP the .fxl file so it can be accepted.

------------------------------
Robert Hoy
------------------------------

Original Message:
Sent: 02-23-2021 09:45
From: mark Prewitt
Subject: Access Linework Codes Error

I didn't know that.  Hmm. 

No matter what code I use, it gives the same error, though.

------------------------------
mark Prewitt

Original Message:
Sent: 02-23-2021 09:37
From: Robert Hoy
Subject: Access Linework Codes Error

Did you know that with TA and C3D, you don't need to begin a line (using default settings)?  You only need to end or close a line.  I don't know if using B is adding to your problem or not.

------------------------------
Robert Hoy

Original Message:
Sent: 02-23-2021 07:08
From: mark Prewitt
Subject: Access Linework Codes Error

Hopefully, someone can help with this;
I have been using codes and linework commands for  quite awhile, but I've been using Survey Pro for the vast majority of time.  I have an .FXL file that contains linework codes and feature definition codes already (and loaded properly on my TSC7).  

I've now started implementing Access for my boundary and topo type work, though.  Everything seems okay, but when I started adding to my groups for Measure Codes (i.e., 5x5, 4x5...) Access doesn't seem to like the way I've entered my codes.  I've entered my codes like this:

132 B (132 is EP and B is Begin)
132
132 E (E is End)
132 CLS (CLS is Close)
…and so on.

When I try to take a shot using this method, Access has a window that pops up and says, "Error-132 B does not contain any line features"

I've gone back to my .fxl and verified that it is properly input and it is.  This is the same feature code file I've used for many years.

My assumption would be that the CAD toolbar is having some effect on my code input?  

Ultimately, I don't care how Access deals with my codes/linework commands, though (at least I don't THINK I care).  I process all my data using Civil 3d - which has worked perfectly for me for many years.  I merely want my points to be measured the way I have them input, so I can export an ASCII file upon completion of fieldwork and import that directly into C3D.

------------------------------
MP (NV)
------------------------------

i have not tested it. but i would like to take a guess that your problem is that you are using numeric codes. the measure codes feature in access has a handy function to increase the number of a code. so if your code is EP, you can add 1 to it, so it would quickly change it to EP1. then EP2 and so on. i could see a conflic if you are using numeric codes because your code 132 would change to 1321 which could be a different code. 

i would agree with other comments that you do not need to use the B and E comands to start end a line. lines start automatically and by adding the numeric identifier to the code(EP1) you can run multiple lines with the same code at the same time(EP2). but if you are used to using the begin and end lines comand it is more likely that you would choose not to use the end comand in the field and instead just start a new line with the begin comand(the line behind you will end on it s own). from what i have seen you do need to add your close command CLS if you want to close a shape.

access does not seem as good as survey pro to add the line control, but i am using the older version of the software on a tsc3 controller and you have to know the control code or find it in the list. and the offsets are not as obvious. they are entered as EP OFFSETCODE 1.0 for a positive offset and EP OFFSETCODE -1.0 for a negative and negative is left of the line for a horizontal offset. 

sorta got into some other topics here. but hopefully this helps.

------------------------------
ian bissonnette
------------------------------

Original Message:
Sent: 02-23-2021 13:30
From: Robert Hoy
Subject: Access Linework Codes Error

You should be able to upload a file to here, you'll just have to ZIP the .fxl file so it can be accepted.

------------------------------
Robert Hoy

Original Message:
Sent: 02-23-2021 09:45
From: mark Prewitt
Subject: Access Linework Codes Error

I didn't know that.  Hmm. 

No matter what code I use, it gives the same error, though.

------------------------------
mark Prewitt

Original Message:
Sent: 02-23-2021 09:37
From: Robert Hoy
Subject: Access Linework Codes Error

Did you know that with TA and C3D, you don't need to begin a line (using default settings)?  You only need to end or close a line.  I don't know if using B is adding to your problem or not.

------------------------------
Robert Hoy

Original Message:
Sent: 02-23-2021 07:08
From: mark Prewitt
Subject: Access Linework Codes Error

Hopefully, someone can help with this;
I have been using codes and linework commands for  quite awhile, but I've been using Survey Pro for the vast majority of time.  I have an .FXL file that contains linework codes and feature definition codes already (and loaded properly on my TSC7).  

I've now started implementing Access for my boundary and topo type work, though.  Everything seems okay, but when I started adding to my groups for Measure Codes (i.e., 5x5, 4x5...) Access doesn't seem to like the way I've entered my codes.  I've entered my codes like this:

132 B (132 is EP and B is Begin)
132
132 E (E is End)
132 CLS (CLS is Close)
…and so on.

When I try to take a shot using this method, Access has a window that pops up and says, "Error-132 B does not contain any line features"

I've gone back to my .fxl and verified that it is properly input and it is.  This is the same feature code file I've used for many years.

My assumption would be that the CAD toolbar is having some effect on my code input?  

Ultimately, I don't care how Access deals with my codes/linework commands, though (at least I don't THINK I care).  I process all my data using Civil 3d - which has worked perfectly for me for many years.  I merely want my points to be measured the way I have them input, so I can export an ASCII file upon completion of fieldwork and import that directly into C3D.

------------------------------
MP (NV)
------------------------------

You do need to end lines, for TA and C3D, if you are reusing line numbers as I do, e.g. EP1 E and next point EP1 (which begins EP1 again).  I find it too confusing to keep adding to line numbers so I don't end up with EP45. I end lines and reuse the line number to keep track of which line number is where, i.e. pavement line and curb line numbers are always together. The TSC7 map is great to zoom around to see which code and line number you were using last, but it's even easier to manage your line numbers using the same range of lines on each side of the road (which is what I usually map).

------------------------------
Robert Hoy
------------------------------

Original Message:
Sent: 02-24-2021 09:52
From: ian bissonnette
Subject: Access Linework Codes Error

i have not tested it. but i would like to take a guess that your problem is that you are using numeric codes. the measure codes feature in access has a handy function to increase the number of a code. so if your code is EP, you can add 1 to it, so it would quickly change it to EP1. then EP2 and so on. i could see a conflic if you are using numeric codes because your code 132 would change to 1321 which could be a different code. 

i would agree with other comments that you do not need to use the B and E comands to start end a line. lines start automatically and by adding the numeric identifier to the code(EP1) you can run multiple lines with the same code at the same time(EP2). but if you are used to using the begin and end lines comand it is more likely that you would choose not to use the end comand in the field and instead just start a new line with the begin comand(the line behind you will end on it s own). from what i have seen you do need to add your close command CLS if you want to close a shape.

access does not seem as good as survey pro to add the line control, but i am using the older version of the software on a tsc3 controller and you have to know the control code or find it in the list. and the offsets are not as obvious. they are entered as EP OFFSETCODE 1.0 for a positive offset and EP OFFSETCODE -1.0 for a negative and negative is left of the line for a horizontal offset. 

sorta got into some other topics here. but hopefully this helps.

------------------------------
ian bissonnette

Original Message:
Sent: 02-23-2021 13:30
From: Robert Hoy
Subject: Access Linework Codes Error

You should be able to upload a file to here, you'll just have to ZIP the .fxl file so it can be accepted.

------------------------------
Robert Hoy

Original Message:
Sent: 02-23-2021 09:45
From: mark Prewitt
Subject: Access Linework Codes Error

I didn't know that.  Hmm. 

No matter what code I use, it gives the same error, though.

------------------------------
mark Prewitt

Original Message:
Sent: 02-23-2021 09:37
From: Robert Hoy
Subject: Access Linework Codes Error

Did you know that with TA and C3D, you don't need to begin a line (using default settings)?  You only need to end or close a line.  I don't know if using B is adding to your problem or not.

------------------------------
Robert Hoy

Original Message:
Sent: 02-23-2021 07:08
From: mark Prewitt
Subject: Access Linework Codes Error

Hopefully, someone can help with this;
I have been using codes and linework commands for  quite awhile, but I've been using Survey Pro for the vast majority of time.  I have an .FXL file that contains linework codes and feature definition codes already (and loaded properly on my TSC7).  

I've now started implementing Access for my boundary and topo type work, though.  Everything seems okay, but when I started adding to my groups for Measure Codes (i.e., 5x5, 4x5...) Access doesn't seem to like the way I've entered my codes.  I've entered my codes like this:

132 B (132 is EP and B is Begin)
132
132 E (E is End)
132 CLS (CLS is Close)
…and so on.

When I try to take a shot using this method, Access has a window that pops up and says, "Error-132 B does not contain any line features"

I've gone back to my .fxl and verified that it is properly input and it is.  This is the same feature code file I've used for many years.

My assumption would be that the CAD toolbar is having some effect on my code input?  

Ultimately, I don't care how Access deals with my codes/linework commands, though (at least I don't THINK I care).  I process all my data using Civil 3d - which has worked perfectly for me for many years.  I merely want my points to be measured the way I have them input, so I can export an ASCII file upon completion of fieldwork and import that directly into C3D.

------------------------------
MP (NV)
------------------------------

Robert,

I appreciate your input.  I believe I have figured out what the problem is (with Shane's help).  I haven't setup my Line Feature Definitions - in fact I didn't even know they existed until this morning.  Unfortunately, it would appear that I MUST have those completed prior to utilizing my linework codes in Measure Codes.

As far as starting and ending linework in C3D goes, I remember when I was first setting up my templates (2008-2009) I turned off the feature that says start linework with "like" codes.  That feature was not useful for me.  That will certainly allow for linework without a beginning linework code, though.

In any case, I appreciate your responses!  Now I have work to do on my .fxl file - having ignorance sucks!  

Take it easy!

------------------------------
mark Prewitt
------------------------------

Original Message:
Sent: 02-24-2021 11:13
From: Robert Hoy
Subject: Access Linework Codes Error

You do need to end lines, for TA and C3D, if you are reusing line numbers as I do, e.g. EP1 E and next point EP1 (which begins EP1 again).  I find it too confusing to keep adding to line numbers so I don't end up with EP45. I end lines and reuse the line number to keep track of which line number is where, i.e. pavement line and curb line numbers are always together. The TSC7 map is great to zoom around to see which code and line number you were using last, but it's even easier to manage your line numbers using the same range of lines on each side of the road (which is what I usually map).

------------------------------
Robert Hoy

Original Message:
Sent: 02-24-2021 09:52
From: ian bissonnette
Subject: Access Linework Codes Error

i have not tested it. but i would like to take a guess that your problem is that you are using numeric codes. the measure codes feature in access has a handy function to increase the number of a code. so if your code is EP, you can add 1 to it, so it would quickly change it to EP1. then EP2 and so on. i could see a conflic if you are using numeric codes because your code 132 would change to 1321 which could be a different code. 

i would agree with other comments that you do not need to use the B and E comands to start end a line. lines start automatically and by adding the numeric identifier to the code(EP1) you can run multiple lines with the same code at the same time(EP2). but if you are used to using the begin and end lines comand it is more likely that you would choose not to use the end comand in the field and instead just start a new line with the begin comand(the line behind you will end on it s own). from what i have seen you do need to add your close command CLS if you want to close a shape.

access does not seem as good as survey pro to add the line control, but i am using the older version of the software on a tsc3 controller and you have to know the control code or find it in the list. and the offsets are not as obvious. they are entered as EP OFFSETCODE 1.0 for a positive offset and EP OFFSETCODE -1.0 for a negative and negative is left of the line for a horizontal offset. 

sorta got into some other topics here. but hopefully this helps.

------------------------------
ian bissonnette

Original Message:
Sent: 02-23-2021 13:30
From: Robert Hoy
Subject: Access Linework Codes Error

You should be able to upload a file to here, you'll just have to ZIP the .fxl file so it can be accepted.

------------------------------
Robert Hoy

Original Message:
Sent: 02-23-2021 09:45
From: mark Prewitt
Subject: Access Linework Codes Error

I didn't know that.  Hmm. 

No matter what code I use, it gives the same error, though.

------------------------------
mark Prewitt

Original Message:
Sent: 02-23-2021 09:37
From: Robert Hoy
Subject: Access Linework Codes Error

Did you know that with TA and C3D, you don't need to begin a line (using default settings)?  You only need to end or close a line.  I don't know if using B is adding to your problem or not.

------------------------------
Robert Hoy

Original Message:
Sent: 02-23-2021 07:08
From: mark Prewitt
Subject: Access Linework Codes Error

Hopefully, someone can help with this;
I have been using codes and linework commands for  quite awhile, but I've been using Survey Pro for the vast majority of time.  I have an .FXL file that contains linework codes and feature definition codes already (and loaded properly on my TSC7).  

I've now started implementing Access for my boundary and topo type work, though.  Everything seems okay, but when I started adding to my groups for Measure Codes (i.e., 5x5, 4x5...) Access doesn't seem to like the way I've entered my codes.  I've entered my codes like this:

132 B (132 is EP and B is Begin)
132
132 E (E is End)
132 CLS (CLS is Close)
…and so on.

When I try to take a shot using this method, Access has a window that pops up and says, "Error-132 B does not contain any line features"

I've gone back to my .fxl and verified that it is properly input and it is.  This is the same feature code file I've used for many years.

My assumption would be that the CAD toolbar is having some effect on my code input?  

Ultimately, I don't care how Access deals with my codes/linework commands, though (at least I don't THINK I care).  I process all my data using Civil 3d - which has worked perfectly for me for many years.  I merely want my points to be measured the way I have them input, so I can export an ASCII file upon completion of fieldwork and import that directly into C3D.

------------------------------
MP (NV)
------------------------------