Issue with CASE Tool

Welcome to LawsonTalk. We hope you enjoy your visit.

You're currently viewing our forum as a guest. This means you are limited to certain areas of the board and there are some features you can't use. If you join our community, you'll be able to access member-only sections, and use many member-only features such as customizing your profile, sending personal messages, and voting in polls. Registration is simple, fast, and completely free. After registration, please check your e-mail within 24 hours for an message from us, read it, and reply to it.

Join our community!

If you're already a member please log in to your account to access all of our features:

Issue with CASE Tool; Quick Painting Problem
Topic Started: Nov 11 2009, 04:43 AM (103 Views)
atl_chris	Nov 11 2009, 04:43 AM Post #1
Newbie Posts: 1 Group: Members Member #14,872 Joined: June 15, 2009	I'm having an issue with the CASE tool. I have a rather basic, if somewhat long, custom table (which also has a long, six field index) defined with dbdef on which I'm trying to generate a simple inquiry form. I've attempted to use Quick Paint, Selective Quick Paint and just painting the form myself. No matter what I try, I get the following error message when I try to save from the CASE tool: Quote: Processing Binary For Interpreter... Key Protected Fields Don't Fit On Line 2 and 1 Short 2 Characters; Adjust Form And Save Again Interpretive Binary Form Not Saved Needless to say, I can't generate the source files. I don't think it's a problem with our environment because I can still paint forms against other Lawson tables and other custom tables we defined with dbdef. Help! Any ideas???



trezaei	Nov 13 2009, 10:30 AM Post #2
LawsonTalk Addict! Posts: 329 Group: Members Member #369 Joined: January 23, 2006	yes, the form paint only lets you put (I believe) 60 characters across a page. (Maybe 80 I don't recall) So here are some possible solutions: 1) Create some tabs and put the fields there 2) Don't use quick paint, just use paint and manually place the fields you need where you need them 3) With #2 you can choose to paint the fields smaller than the DB size Those are just three tricks on how to get past that issue.


« Previous Topic · Coding, Program Errors and Bugs · Next Topic »