Output Data To Word Document
-
Sure you can, Right click Merge two or more cells.
-
This is the word document:
The problem I have in Excel is making look exactly like this...if I could, I could just make a few Macros for numbering the sheets and be done with it. But I couldn't get my tables to individually widen without affecting the main column...for example, Description being wider than the SALESPERON field...
-
Quickly looking at this, I'd have:
JOB ID be the width of columns A and B,
Description be the width of C and D.
Date Ordered shrunk down to E only
and leave Date Complete to F and G.So you'd need to Merge A and B for Job ID
Merge C and D for Description
Date Ordered would remain the same same column for E
Date Complete would be merged for F and GYes it will be a little different, but you're filling this out on a computer now, it can afford to be.
-
InfoPath?
-
@Dashrender said:
Quickly looking at this, I'd have:
JOB ID be the width of columns A and B,
Description be the width of C and D.
Date Ordered shrunk down to E only
and leave Date Complete to F and G.So you'd need to Merge A and B for Job ID
Merge C and D for Description
Date Ordered would remain the same same column for E
Date Complete would be merged for F and GYes it will be a little different, but you're filling this out on a computer now, it can afford to be.
Excellent...let me give it a shot...different is something our HR person doesn't care for much...
-
@Dashrender said:
Quickly looking at this, I'd have:
JOB ID be the width of columns A and B,
Description be the width of C and D.
Date Ordered shrunk down to E only
and leave Date Complete to F and G.So you'd need to Merge A and B for Job ID
Merge C and D for Description
Date Ordered would remain the same same column for E
Date Complete would be merged for F and GYes it will be a little different, but you're filling this out on a computer now, it can afford to be.
This is what my work in progress spreadsheet looks like (with semi-private info blanked out)...I assume I may need to start over if I do some merging?
-
You can unmerge if needed.
-
@Dashrender said:
You can unmerge if needed.
All things said.. you're probably better off with Access or something else.
-
@Dashrender said:
@Dashrender said:
You can unmerge if needed.
All things said.. you're probably better off with Access or something else.
Yeah. going to try Access...it seems like a step backward but they don't call Office "Office" for no reason. It for sure helps us in a small business.
-
@garak0410 said:
Yeah. going to try Access...it seems like a step backward but they don't call Office "Office" for no reason. It for sure helps us in a small business.
Why do you see Access as a step backwards?
-
@garak0410 It's not really a step backwards, but a step forward.
Think of it this way... instead of saving every single form you create in word every day, and then spending the time to search said selection of forms, you can dump all of this into a database.
Investing time on the front end of this project will save you boat-loads of time on the back end.
And you've got your database tables already created for the most part... time to just change that form into tables and then write the report against it....
(assuming you don't have anything like that in place already.)
-
@Dashrender said:
@garak0410 said:
Yeah. going to try Access...it seems like a step backward but they don't call Office "Office" for no reason. It for sure helps us in a small business.
Why do you see Access as a step backwards?
Oh from the various advice I get from the forums when seeking development suggestions. Every time I seek Excel/VBA help, someone will usually say RUN from it and get on ASP.NET. Could be trolls?
-
@milnesy said:
@garak0410 It's not really a step backwards, but a step forward.
Think of it this way... instead of saving every single form you create in word every day, and then spending the time to search said selection of forms, you can dump all of this into a database.
Investing time on the front end of this project will save you boat-loads of time on the back end.
And you've got your database tables already created for the most part... time to just change that form into tables and then write the report against it....
(assuming you don't have anything like that in place already.)
That's the direction I am going. :)...per my previous comment, I've not approached Access much at all because so many people say go web based. Well, I am still not an expert developer so I need easy right now. I did start to use Access yesterday for this form from Dashrender's suggestion and it looks like it will work for me...
-
@garak0410 said:
Oh from the various advice I get from the forums when seeking development suggestions. Every time I seek Excel/VBA help, someone will usually say RUN from it and get on ASP.NET. Could be trolls?
Kind of. Possibly just people who don't really have a good grasp on how this stuff works and want to post something. VBA cannot be easily replaced. They are probably confusing it with VB, which should always be replaced. Or just trolls.
-
@garak0410 said:
@Dashrender said:
@garak0410 said:
Yeah. going to try Access...it seems like a step backward but they don't call Office "Office" for no reason. It for sure helps us in a small business.
Why do you see Access as a step backwards?
Oh from the various advice I get from the forums when seeking development suggestions. Every time I seek Excel/VBA help, someone will usually say RUN from it and get on ASP.NET. Could be trolls?
If you're comfortable - even if you're not - maybe going with a web frontend and a MySQL DB. It would be nearly universally available. My issue is I barely know where to even begin on a project like that.
-
Excessive use of Access can be a nightmare in organisations. I don't particularly mind IT pros using it, it's when end users starting developing applications in it that things go wrong. I mainly hate it for that reason.
But reports of Access's demise have been greatly exaggerated, although Microsoft seem to be now marketing it more as a Sharepoint app designer than a standalone tool. Are you planning on using it that way?
I prefer everything to be browser based, so no longer use it (other than as a nice front end for SQL Server queries). This is just personal taste, I guess. Mind you, I still develop with classic ASP rather than ASP.net, so I'm still into my ancient technologies.
-
@scottalanmiller said:
@garak0410 said:
Oh from the various advice I get from the forums when seeking development suggestions. Every time I seek Excel/VBA help, someone will usually say RUN from it and get on ASP.NET. Could be trolls?
Kind of. Possibly just people who don't really have a good grasp on how this stuff works and want to post something. VBA cannot be easily replaced. They are probably confusing it with VB, which should always be replaced. Or just trolls.
Pretty much everything is Office here...and with our Exchange Online subscription, we do have SharePoint online which does play nicely with Access. It would take me a few more years of study before I got even one thing off of VBA here. So for now, I will embrace it...
-
@garak0410 said:
@scottalanmiller said:
@garak0410 said:
Oh from the various advice I get from the forums when seeking development suggestions. Every time I seek Excel/VBA help, someone will usually say RUN from it and get on ASP.NET. Could be trolls?
Kind of. Possibly just people who don't really have a good grasp on how this stuff works and want to post something. VBA cannot be easily replaced. They are probably confusing it with VB, which should always be replaced. Or just trolls.
Pretty much everything is Office here...and with our Exchange Online subscription, we do have SharePoint online which does play nicely with Access. It would take me a few more years of study before I got even one thing off of VBA here. So for now, I will embrace it...
I'm not sure that there is any replacement for VBA. You'd have to replace Office entirely, unless I am missing some automation capability.
-
@scottalanmiller said:
@garak0410 said:
@scottalanmiller said:
@garak0410 said:
Oh from the various advice I get from the forums when seeking development suggestions. Every time I seek Excel/VBA help, someone will usually say RUN from it and get on ASP.NET. Could be trolls?
Kind of. Possibly just people who don't really have a good grasp on how this stuff works and want to post something. VBA cannot be easily replaced. They are probably confusing it with VB, which should always be replaced. Or just trolls.
Pretty much everything is Office here...and with our Exchange Online subscription, we do have SharePoint online which does play nicely with Access. It would take me a few more years of study before I got even one thing off of VBA here. So for now, I will embrace it...
I'm not sure that there is any replacement for VBA. You'd have to replace Office entirely, unless I am missing some automation capability.
Our main metal building program has a ton of raw, text based data that is imported into Excel via some very heavy VBA. And when I say heavy, I mean it. It would take me at an expert level to move this to another language and format. So for now, just learning it. And so far, I am liking Access...I think it may work and hope it will work well with SharePoint Online.
-
@garak0410 moving off of MS Office would be huge, I'm sure. Although, in theory, if you are using Access you can put the backend on SQL Server and at least not be tied to JetDB. Then you can use anything to access the data.
