Certain fields get corrupted

[MarMan]

I can't make sense of this. I also do not know if this should be in the Access section. Perhaps if no one knows I could make a new thread in Access.

Using Access 2003.

The problem occurs when I right-click an Access report, then click "Send to" which has only one option of "Mail recipient". Then I click Excel. An outlook window containing an out going mail opens with an Excel attachment.. There is one column with item ids. some get corrupted while others do not. It seems they need to begin with the numerals 20 to get corrupted. Anything else comes out OK

For example, the following item ids are ok
100657
100657-17
216116-115
221007-001
The following get corrupted (the corrupted version follows)
202103-001 becomes 1313049
205103-001 becomes 2408777

Anyone have any idea whats going on?

 

[MarMan]

Hey kid, if you read the post you will see that a field is getting corrupted when it is passed to Excel. File repair is absolutely useless. That is used for a damaged file. That has no impact of fields that are returned from a query just fine. Thanks for trying though unless you are just trying to peddle software.

I wouldn't spend one penny on any Access software since Micorsoft is discontinuing it. Also there will not be a 64-bit jet driver. Anyone who still wishes to use Access will just pay more later if they do not dump it now.

And for the record, I found the problem with the fields. Excel was assuming some part numbers were dates and converting only those.

 

[Galaxiom]

The following get corrupted (the corrupted version follows)
202103-001 becomes 1313049
205103-001 becomes 2408777

I can't quite place it exactly but I expect Windows is doing one of its "helpful" second guessing tricks.

202103-001 is not unlike some kind of date format. Windows does some evil stuff with things it thinks might be dates.

When processing an import or an export Access and Excel look at a limited number of records then decide on the datatype of the field/column and then try to force the rest of the data to fit.

 

[Galaxiom]

BTW. The myth about Microsoft dropping Access has been going around almost since Access was first released.

 

[MarMan]

Yes, it does think its a date. But the interesting thing is that it does not convert the column, it does this on a field by field basis. I don't know the specifics, but it seems approximately 50 years around 2013xx-xxx becomes a date conversion. Any other field remains untouched.

And you are correct, there was a myth about access going away. Its a fact now. I don't know what kind of company would allow mission critical applications to be limited to the 32-bit subsystem but I suspect not one that takes IT (and profits) seriously.

I know Access gurus don't want to believe it and you can deny it. If you're close to retiring it doesn't matter. If you want a future then you must evolve with the rest of the world.

 

[Galaxiom]

And you are correct, there was a myth about access going away. Its a fact now.

How about some evidence to support your unsubstantiated assertion?

Fact is that Access 16 is already in development.
http://answers.microsoft.com/en-us/...a3?msgId=c7101bc0-de59-4216-9bcc-d4ec9414d41c

(Bob is a member at this forum and is far more connected to Microsoft than you are ever likely to be.)

I don't know what kind of company would allow mission critical applications to be limited to the 32-bit subsystem but I suspect not one that takes IT (and profits) seriously.

Showing off your superior knowledge? There is already a 64 bit version of Access.

I know Access gurus don't want to believe it and you can deny it. If you're close to retiring it doesn't matter. If you want a future then you must evolve with the rest of the world.

I can see you will go a long way on this site.

 

[MarMan]

@Galaxiom: I will piece it together for you since you can't seem to grasp the reality.

The reason Access is still alive is because so many businesses use it. As the PC dies business will be the driving force. (And before you get the wrong idea AGAIN when computer professionals talk about the PC dying it doesn't mean that the PC is going away, thats what users think. It means the PC is going away as the #1 tool for web, e-mail, documents, games and other uses that it was once king of.).

Another fact that you don't seem to be aware of is that the majority of business uses of Access use Access on the backend. (Backend means that they never run the Access exe, they just use the database). The way Access is accessed is via the jet driver. There is no 64-bit jet driver and there will never be one. This is a nail in the coffin that your affinity for Access blinds you to see. It is very important to pay attention to these key issues if you are a professional developer. If you are not a professional then it does not matter.

So what does Microsoft recommend? Use SQL Server Express or Compact.

I know Bloomingdales has moved at least one system off of Access. Fitlinxx, a company that puts computers on weight machines also has moved away from Access. The Intuitive ERP system is moving away from Access as we speak. And these are just things I learned while getting work done. I'm sure if I cared enough to look I would find numerous examples but I won't. I was only trying to help you but I can't help someone who doesn't want to help themselves.

Micorsoft has learned that it is not cost effective to produce competing products. Remember Win 95 and NT? You may be too young judging by the inexperienced nature of your comments so I will tell you. Micorsoft had two flavors of windows that they merged into one, keeping the stronger one which was NT. Since SQL server is far superior a database product than Access, Microsoft plans to eliminate Access in the future.

Micorsoft also doesn't want to alienate the users who know Access but have never used a real database so they must make them WANT to switch. One way to do this is to kill the jet driver.. Any smart developers will migrate to SQL server. Any stubborn, less skilled or lacking vision developers will stay with Access and convert the code to use the new driver. Its one way to keep the skilled developers liking Microsoft and the others, well its no major loss since they can't evolve with the times they will probably not go far anyway.

I probably said too much but you get the point.

(Bob is a member at this forum and is far more connected to Microsoft than you are ever likely to be.)

Pure ignorance coming from someone who has no idea who they are talking to. LOL If you only knew. . .

 

[MartynE]

Pure ignorance coming from someone who has no idea who they are talking to. LOL If you only knew. . .

Enlighten us, by telling us who you are..?
I'm getting the popcorn, please continue.

 

[RainLover]

Enlighten us, by telling us who you are..?
I'm getting the popcorn, please continue.

Don't bother with the popcorn. Galaxiom is too smart to waste his time here. This guy reminds me of Solo something. Full of puff and wind. Next thing he will be telling me that my copy of 97 won't work.

 

[Galaxiom]

I don't really need to reply. Anyone who actually knows anything about the subject would only need read MarMan's post to immediately see that he is a jumped up fool.