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!

Register Log in
  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Remote View -- Line Too Long

Status
Not open for further replies.
gregjohn

gregjohn

Technical User
Joined
Aug 13, 2001
Messages
29
Location
US
I am in the process of converting vfp tables to sql server express. I have the connection made and have used remote views. For several tables this works fine.

However, I have a few tables that, have very long field names. When I try to create the remote view I receive an error that "line is too long". I am assuming this means the field name as opposed to the number of fields which is about 245. Is that correct? (In looking at the "view sql", I see it has truncated several of the field names).

Also, if it is the length of the field is there any way around it without having to go through and rename everything?

Thanks for any help.

Greg
 
Sort by date Sort by votes
You didn't say what version of VFP you're using, but in VFP9 the maximum length of a field name is 128 characters, the maximum number of fields in a select statement is 255, and the maximum number of characters in a command line or macro substituted line is 8,192.

When you say the number of fields in the view is about 245, are they all coming from one table? If so, I'd take a long, hard look at normalising that table. And if they're coming from multiple tables, what are you going to do with all that data in one view?

Good luck,
Jim
 
Upvote 0 Downvote
I am using vfp 8 and a single table. Do you know if the lengths you described for vfp 9 are the same for 8?

While my fields are long, they are not 128 characters. The fields exist in a table right now.
 
Upvote 0 Downvote
Yes, those are the same in VFP8. Probably you're bumping up against the command line limitation of 8,192 characters. You might need to do something like the following.
Code: 
LOCAL lnH1, lcSql, lnResult

lnH1 = SQLSTRINGCONNECT(Add in your connection string here)

TEXT TO lcSql NOSHOW PRETEXT 7
*(Create SQL View text goes here)
ENDTEXT

lnResult = SQLEXEC(lnH1, lcSql)
But again, I'd urge you to look at normalising that data.

Regards,
Jim
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

T
  • Locked
  • Question Question
long vs short filenames
2
Replies
20
Views
3K
Joe Crescenzi
Joe Crescenzi
stanlyn
  • Locked
  • Question Question
String is Too Long To Fit
2
Replies
20
Views
2K
stanlyn
stanlyn
Filip Brnic
  • Locked
  • Question Question
Help with setting up the report (error message band 1 is too large to fit
Replies
8
Views
2K
Chris Miller
Chris Miller
Nro
  • Locked
  • Question Question
Parametrized view response time too long
Replies
17
Views
775
Nro
Nro
J
  • Locked
  • Question Question
FGETS() after reading a file line, is inserting a blank character after each valid character.
Replies
5
Views
2K
JoseGala
J

Part and Inventory Search

Sponsor

Back
Top